feat: allow using a chainId or networkClientId to fetch top assets

[infiniteflower]

Explanation

This PR allows passing in either a chainId or a networkClientId to fetchTopAssets. Previously only networkClientId was allowed.

This is to support the case of Bridge where a user could select a destination chain that they have not added to MM yet, there by not having a networkClientId to provide. The user will have a destination chainId that we want to look up top assets on.

References

Related to MetaMask/metamask-mobile#14258

Changelog

@metamask/swaps-controller

• CHANGED: Allow passing in either a chainId or a networkClientId to fetchTopAssets. Previously only networkClientId was allowed.

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 highlighted breaking changes using the "BREAKING" category above as appropriate
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes