fix(tron-wallet-snap): use scopes from the snap manifest for discovery/account creation

[hmalik88]

Explanation

The source of truth for a snap's supported scopes should be the manifest. The tron snap was incorrectly using hardcoded values (which included testnets), this was caught at the client level because we started to see a perf regression in the onboarding wallet numbers.

References

N/A

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
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

[hmalik88]

Having to cast here because there's a mismatch between the readonly Network[] type and KeyringAccount's scopes property. I'm going to review usage of the property across our architecture and possibly tighten the type upstream.

[hmalik88]

@metamaskbot publish-preview

[github-actions]

Preview builds have been published. Learn how to use preview builds in other projects.

Expand for full list of packages and versions.

@metamask-previews/bitcoin-wallet-snap@2.0.1-preview-563752c
@metamask-previews/snap-networks-utils@1.0.0-preview-563752c
@metamask-previews/solana-wallet-snap@5.0.1-preview-563752c
@metamask-previews/tron-wallet-snap@3.0.0-preview-563752c