L2-L1 transactions not recognized in the rgbpp activity API

[ShookLyngs]

Currently, only L1-L1 and L1-L2 transactions are recognized in the /rgbpp/v1/address/{btc_address}/activity API, while L2-L1 transactions are marked as isRgbpp: false in the API response. This is expected because it is difficult to determine if each BTC_TX has an isomorphic transaction on L2.

For example, you can query the following BTC address on btc-assets-api testnet:

• Route: https://api.testnet.rgbpp.io/rgbpp/v1/address/tb1qrkh7g0gkllttvsu9kzm7f5c25agnj8ype88xsg/activity
• TxId: a02f0653120e49b56817e528472352c7d96758c0b3a0676e6dc3f556acb6db55