## Explanation

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->
Updates `bridge-controller`, `preferences-controller`,
`transactions-controller` and `assets-controllers` for enabling HyperEVM
support in those controllers.
Main PRs:
- Preference and Transaction controller:
#7770
- Assets Controllers : #7790
- Bridge Controller: #7787

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

## 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](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md)
- [ ] I've introduced [breaking
changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md)
in this PR and have prepared draft pull requests for clients and
consumer packages to resolve them


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Primarily a release/version and dependency bump across multiple
controller packages; functional risk is low, but updating
`@metamask/transaction-controller` across many consumers can surface
integration/behavior changes at runtime.
> 
> **Overview**
> Bumps the monorepo version to `781.0.0` and cuts new releases for
`@metamask/transaction-controller@62.13.0`,
`@metamask/preferences-controller@22.1.0`,
`@metamask/assets-controllers@99.2.0`, and
`@metamask/bridge-controller@65.2.0` (with changelog entries updated
accordingly).
> 
> Updates downstream packages to consume the new controller
versions—most notably raising `@metamask/transaction-controller` to
`^62.13.0` across bridge, status, earn, middleware, phishing, shield,
subscription, and user-operation controllers—and refreshes `yarn.lock`
to match.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
ccf4fe5. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->