Integrate patch changes into core codebase

[amitabh94]

Explanation

The mobile codebase currently relies on a patch (@metamask+assets-controllers+73.0.2.patch) to modify @metamask/assets-controllers and @metamask/preferences-controller. This patch introduces a new preference for displaying NFT media, removes OpenSea-specific API key handling, and adds a preference for safe chains list validation. The goal of this PR is to incorporate these changes directly into the core packages to eliminate the need for this mobile patch, simplifying maintenance and ensuring consistency across platforms.

This PR implements the following changes:

• Renames openSeaEnabled to displayNftMedia: This change is applied across NftController (in @metamask/assets-controllers) and PreferencesController (in @metamask/preferences-controller), including state, methods, and tests. Backward compatibility for openSeaEnabled is maintained during the transition to prevent immediate breaking changes for consumers.
• Removes OpenSea API key handling: The setApiKey method and openSeaApiKey state are removed from NftController.
• Adds useSafeChainsListValidation: A new state property and its corresponding setter are introduced in PreferencesController.

The rename from openSeaEnabled to displayNftMedia is a semantic shift to broaden the scope beyond OpenSea and prepare for future NFT API integrations, decoupling the display logic from a specific provider. The removal of OpenSea API key functionality aligns with this broader strategy. Changes span assets-controllers and preferences-controller because NftController consumes preferences managed by PreferencesController.

References

• Inspired by fix(assets): implement missing patch changes to nft and preferences controllers #4774
• Eliminates the need for the mobile patch: @metamask+assets-controllers+73.0.2.patch
• The @metamask+assets-controllers++multiformats+13.3.2.patch is a separate dependency/bundler issue that will be addressed by subsequent dependency bumps or removal in mobile after this PR is merged and published.

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

---

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}