chore: the address of keychain internal also tweak

[Crayon-Shin-chan-bitlightlabs]

We integrated the taproot advanced script with RGB, such as HTLC script. When we perform refund or redeem operations, we need to transfer the corresponding BTC to the keychain internal that bp wallet will known these utxos

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 2.8%. Comparing base (55a814a) to head (b08fdfa).
Report is 2 commits behind head on master.

Files with missing lines	Patch %	Lines
src/descriptor.rs	0.0%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #273     +/-   ##
=======================================
- Coverage     2.8%   2.8%   -0.0%     
=======================================
  Files          15     15             
  Lines        1914   1921      +7     
=======================================
  Hits           53     53             
- Misses       1861   1868      +7     

Flag	Coverage Δ
rust	2.8% <0.0%> (-<0.1%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[St333p]

I don't see issues with this proposal, as there may be cases in which it's necessary to add the tapret tweak on an output whose address doesn't belong to the tapret keychain. I'd even argue we could skip the check on the keychain altogether, giving more freedom to wallet developers to manage keychains as they see fit. Those not needing the additional freedom can always avoid receiving on tweaked addresses belonging to unexpected keychains.

[dr-orlovsky]

Yes, let's skip the check altogether then. Also, in v0.12 there is no such thing anyway

[dr-orlovsky]

Why did you close the PR? It was fine, you've could just add a commit removing the check on top...

[Crayon-Shin-chan-bitlightlabs]

Why did you close the PR? It was fine, you've could just add a commit removing the check on top...

i have tried to fix it, but the deprecated strict_serialize_type i can't fix. because that need to modify the upstream strict_types