chore: bump uuid from ^8.3.2 to ^9.0.1

[cryptodev-2s]

Explanation

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
Dependency-only major bump with no source edits; risk is mainly if uuid v9 behavior or bundling differs from v8 in downstream clients, though usage here is standard v4 generation.

Overview
This PR standardizes the monorepo on uuid v9 by bumping uuid from ^8.3.2 to ^9.0.1 in the root devDependencies and across many @metamask/* packages that depend on it directly.

Where packages typed against UUIDs, @types/uuid is updated from ^8.3.0 to ^9.0.8, and the lockfile drops the old @types/uuid@^8.3.0 entry. Affected packages record the bump under [Unreleased] in their changelogs; there are no runtime or import changes in this diff—existing v4 ESM imports stay as-is.

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

[cryptodev-2s]

@metamaskbot update-changelogs

[cryptodev-2s]

@metamaskbot update-changelogs

[cryptodev-2s]

@metamaskbot update-changelogs

[cryptodev-2s]

@metamaskbot update-changelogs

[metamask-ci]

✅ Changelogs updated and pushed.