Update cell status of BTC address detail asset RGB++ Tab

[Sven-TBD]

异常解绑状态的Cell 其原Owner 地址无法正常使用此资产，因此对该地址进行资产统计、资产展示时，应该去掉异常解绑的资产，同时可考虑将此类资产单独展示。 针对这一场景，先对BTC 地址详情页作出如下调整：

1. BTC 地址详情页的 Live Cell Tab 不应包含 异常解绑的资产
2. BTC 地址详情页的 XUDT Tab 统计不应包含 异常解绑的资产
3. BTC 地址详情页的 RGB++ Tab 统计不应包含 异常解绑的资产
4. BTC 地址详情页的 Invalid Tab 应包含 异常解绑的资产

Cells with abnormal unbinding status have assets that cannot be normally used by their original Owner addresses. Therefore, when conducting asset statistics and displaying assets for these addresses, the assets with abnormal unbinding should be excluded. Additionally, such assets can be considered for separate display.

For this scenario, make the following adjustments to the BTC address details page:

1. The Live Cell Tab on the BTC address details page should not include assets with abnormal unbinding.
2. The XUDT Tab on the BTC address details page should not include assets with abnormal unbinding.
3. The RGB++ Tab on the BTC address details page should not include assets with abnormal unbinding.
4. The Invalid Tab on the BTC address details page should include assets with abnormal unbinding.

[Sven-TBD]

@Kirl70 Hi Kirl, Please add a Tab on BTC address detail page @Daryl-L @rabbitz You can go on this issue based on the description above

[Kirl70]

Design Draft: https://www.figma.com/design/6XNoimRDbFTTNm016rbIdU/Magickbase?node-id=38041%3A23386&t=dVzUoYQXiAvJDFhL-1

[rabbitz]

PR: https://github.com/nervosnetwork/ckb-explorer/pull/1871

/api/v1/address_live_cells/{{id}} The interface adds an optional filtering field bound_status, the optional value is:

• bound: Bound
• unbound: Abnormal unbinding

[rabbitz]

Query btc address unbound live cells count

https://github.com/nervosnetwork/ckb-explorer/pull/1875

GET /api/v2/bitcoin_addresses/{{id}}

[Daryl-L]

https://github.com/Magickbase/ckb-explorer-frontend/pull/344

[FrederLu]

Magickbase/ckb-explorer-frontend#344

The data of the previous abnormal unbinding is displayed abnormally. After the current synchronization BTC UTXO service is redeployed, the previous data needs to be resynchronized and then confirmed. @Daryl-L