Release/1005.0.0

[bergarces]

Explanation

Minor bump for assets-controller. Changes already patched in main.

References

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
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Low Risk
Version, changelog, and lockfile-only release with no new application logic in the diff; the shipped 8.1.0 AssetsController isEnabled changes are minor behavioral fixes already on main.

Overview
Cuts release 1005.0.0 for the core monorepo and publishes @metamask/assets-controller 8.1.0 (from 8.0.2), with changelog entries moved from Unreleased into the 8.1.0 section.

That release documents behavior already on main: AssetsController re-checks isEnabled when data sources report active chain updates, and no longer bails out of constructor setup when isEnabled is false at first construction so tracking can start once it becomes true.

@metamask/bridge-controller and @metamask/transaction-pay-controller bump their @metamask/assets-controller dependency to ^8.1.0; yarn.lock is updated accordingly.

^{Reviewed by Cursor Bugbot for commit a434282. Bugbot is set up for automated code reviews on this repo. Configure here.}

[metamaskbotv2]

✅ Changelogs updated and pushed.