feat: register Bitcoin and Tron account provider wrappers

[ulissesferreira]

Explanation

As we move towards the new Account Provider model we must not forget to include Bitcoin and Tron support. These changes are essential to have their accounts automatically discovered on the MetaMask Extension for example.

References

Tron Epic: https://consensyssoftware.atlassian.net/browse/NWNT-410?atlOrigin=eyJpIjoiY2Y5ZjYzYmU1MjBhNGZjNmI3NGE5MGZjMTI1ZDA0ZjciLCJwIjoiaiJ9

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

---

Note

Registers BtcAccountProvider and TrxAccountProvider in MultichainAccountService, wires their configs, and updates tests to mock and validate them.

• MultichainAccountService:
  • Register BtcAccountProvider and TrxAccountProvider alongside existing EvmAccountProvider and SolAccountProvider using AccountProviderWrapper.
  • Extend providerConfigs to accept BtcAccountProvider and TrxAccountProvider configs.
  • Update imports to source providers and types from ./providers.
• Tests (MultichainAccountService.test.ts):
  • Mock BtcAccountProvider and TrxAccountProvider; extend Mocks to include them.
  • Set static NAME constants for BTC/TRX providers in setup.
  • Add mockAccountProvider calls for BTC (BtcAccountType.P2wpkh) and TRX (TrxAccountType.Eoa).
  • Verify provider config forwarding for BTC/TRX and optional config behavior.

^{Written by Cursor Bugbot for commit b0bad50. This will update automatically on new commits. Configure here.}

[ccharly]

Rejecting for now, as we don't want to use those providers without any feature flags for the moment