feat(wallet)!: wire LoggingController into default initialization

[grypez]

Explanation

Wire LoggingController into the default @metamask/wallet initialization so
that its actions and events are exposed on the shared messenger bus:
LoggingController:getState/:stateChange, LoggingController:add, and
LoggingController:clear.

@metamask/wallet is the shared controller-integration layer adopted by
extension, mobile, and other clients, so any constructor value that differs
between clients must be an injectable instanceOptions rather than hardcoded.
For LoggingController there is nothing to inject: both clients construct it
with only messenger and state, and it delegates no external actions/events.
It therefore wires up as a plain namespaced child messenger with no
instanceOptions slot.

Per-environment options

Option	Extension	Mobile	Default
(none)	Constructs with { messenger, state } only	Constructs with { messenger, state } only	Same

There are no injectable options. The extension additionally registers a
runtime.onInstalled listener that emits a version-update log; that is
client-side glue around construction (not a controller constructor option) and
stays in the extension's own adoption layer.

References

• Extension init: https://github.com/MetaMask/metamask-extension/blob/main/app/scripts/messenger-client-init/logging-controller-init.ts
• Extension messenger: https://github.com/MetaMask/metamask-extension/blob/main/app/scripts/messenger-client-init/messengers/logging-controller-messenger.ts
• Mobile init: https://github.com/MetaMask/metamask-mobile/blob/main/app/core/Engine/controllers/logging-controller-init.ts
• Mobile messenger: https://github.com/MetaMask/metamask-mobile/blob/main/app/core/Engine/messengers/logging-controller-messenger.ts
• Issue: N/A

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, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes (N/A — no client currently constructs LoggingController through @metamask/wallet yet; adoption PRs follow separately)

---

Note

Medium Risk
Breaking wallet init change can collide if clients already register LoggingController on the same messenger; behavior is otherwise a standard controller bootstrap with broad test coverage.

Overview
Breaking: Default @metamask/wallet initialization now constructs LoggingController and registers it on the shared messenger (LoggingController:getState, :stateChange, :add, :clear), matching extension/mobile wiring with only messenger and state—no new instanceOptions slot.

Adds the @metamask/logging-controller dependency, a logging-controller initialization instance (exported via instances/index so it joins defaultConfigurations), unit tests for that config, and Wallet integration tests for initial state and messenger routing. Docs/chore: wallet changelog, README dependency graph edge, CODEOWNERS for the init path, and TypeScript project references.

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