refactor: update Nft Controllers to use selectedAccountId instead of selectedAddress

[montelaidev]

Explanation

This PR updates removes selectedAddress and uses the controller messenger to get InternalAccounts in the Nft Controllers

References

Fixeshttps://github.com/MetaMask/accounts-planning/issues/381

Changelog

@metamask/assets-controllers

• BREAKING: NftController constructor argument selectedAddress has been removed.
• BREAKING: NftController now requires AccountsControlelr:get{Account,SelectedAccount} messenger actions.
• BREAKING: NftController now requires AccountsController:selectedEvmAccountChange event.
• BREAKING: NftDetectionController now requires AccountsControlelr:getSelectedAccount messenger actions.

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

[montelaidev]

@metamaskbot publish-preview

[github-actions]

Preview builds have been published. See these instructions for more information about preview builds.

Expand for full list of packages and versions.

{
"@metamask-previews/accounts-controller": "13.0.0-preview-61ace68c",
"@metamask-previews/address-book-controller": "4.0.1-preview-61ace68c",
"@metamask-previews/announcement-controller": "6.1.0-preview-61ace68c",
"@metamask-previews/approval-controller": "6.0.1-preview-61ace68c",
"@metamask-previews/assets-controllers": "28.0.0-preview-61ace68c",
"@metamask-previews/base-controller": "5.0.1-preview-61ace68c",
"@metamask-previews/build-utils": "2.0.1-preview-61ace68c",
"@metamask-previews/composable-controller": "6.0.1-preview-61ace68c",
"@metamask-previews/controller-utils": "9.1.0-preview-61ace68c",
"@metamask-previews/ens-controller": "10.0.1-preview-61ace68c",
"@metamask-previews/eth-json-rpc-provider": "3.0.1-preview-61ace68c",
"@metamask-previews/gas-fee-controller": "15.0.0-preview-61ace68c",
"@metamask-previews/json-rpc-engine": "8.0.1-preview-61ace68c",
"@metamask-previews/json-rpc-middleware-stream": "7.0.1-preview-61ace68c",
"@metamask-previews/keyring-controller": "15.0.0-preview-61ace68c",
"@metamask-previews/logging-controller": "3.0.1-preview-61ace68c",
"@metamask-previews/message-manager": "8.0.1-preview-61ace68c",
"@metamask-previews/name-controller": "6.0.1-preview-61ace68c",
"@metamask-previews/network-controller": "18.1.0-preview-61ace68c",
"@metamask-previews/notification-controller": "5.0.1-preview-61ace68c",
"@metamask-previews/permission-controller": "9.0.2-preview-61ace68c",
"@metamask-previews/permission-log-controller": "2.0.1-preview-61ace68c",
"@metamask-previews/phishing-controller": "9.0.1-preview-61ace68c",
"@metamask-previews/polling-controller": "6.0.1-preview-61ace68c",
"@metamask-previews/preferences-controller": "10.0.0-preview-61ace68c",
"@metamask-previews/queued-request-controller": "0.9.0-preview-61ace68c",
"@metamask-previews/rate-limit-controller": "5.0.1-preview-61ace68c",
"@metamask-previews/selected-network-controller": "12.0.1-preview-61ace68c",
"@metamask-previews/signature-controller": "15.0.0-preview-61ace68c",
"@metamask-previews/transaction-controller": "28.1.0-preview-61ace68c",
"@metamask-previews/user-operation-controller": "8.0.1-preview-61ace68c"
}

[mcmire]

Similar comment as here — what are your thoughts on using the messenger to get this value from the AccountsController a bit later on in this constructor instead of having the constructor take this argument?