chore: explicitly pass networkClientId for nftController

eslint-warning-thresholds.json

@@ -39,13 +39,11 @@
   },
   "packages/assets-controllers/src/NftController.test.ts": {
     "import-x/namespace": 9,
-    "import-x/order": 3,
-    "jest/no-conditional-in-test": 8
+    "jest/no-conditional-in-test": 6
   },
   "packages/assets-controllers/src/NftController.ts": {
     "@typescript-eslint/prefer-readonly": 1,
-    "jsdoc/check-tag-names": 46,
-    "jsdoc/tag-lines": 4
+    "jsdoc/check-tag-names": 46
   },
   "packages/assets-controllers/src/NftDetectionController.test.ts": {
     "import-x/namespace": 6,

packages/assets-controllers/CHANGELOG.md

@@ -9,6 +9,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
+- Updated `NftController` and `NftDetectionController` to eliminate the dependency on the current chain ([#5622](https://github.com/MetaMask/core/pull/5622))
+  - All functions that previously accepted networkClientId as an optional parameter now require it as a mandatory parameter.
 - Refactor `TokensController` to remove reliance on a single selected network ([#5659](https://github.com/MetaMask/core/pull/5659))
   - `TokensController` methods now require `networkClientId` as an explicit parameter.
   - Token management logic is fully parameterized by `chainId`, allowing multi-chain token handling and improving reliability across network changes.