add validation that the nft standard matches the type argument

[adonesky1]

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/854

Currently when wallet_watchAsset is called with type ERC721 or ERC1155, we don't check whether the asset actually matches the type passed - we push it into a flow for suggested NFTs do a bunch of other validation, and if it passes we add it with the correct value for standard even if it doesn't match the type (standard) originally passed in the request. This adds validation of this type.

After:
https://github.com/MetaMask/core/assets/34557516/92a9bba5-c466-4ebc-b82c-b395649be52b

Changelog

@metamask/assets-controllers

• ADDED: Adds validation that the standard of an NFT added via the watchNFT method matches the type argument passed with the request.

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