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
Marked breaking for @metamask/wallet consumers because default initialization and wallet state shape gain LoggingController; scope is limited to standard controller wiring with tests and no injectable options.

Overview
Breaking: @metamask/wallet now initializes LoggingController by default alongside the other bundled controllers, exposing LoggingController:getState, :stateChange, :add, and :clear on the wallet messenger.

The wiring follows the same pattern as controllers like AddressBookController: a new logging-controller initialization instance constructs the controller from messenger and state only, with no instanceOptions slot. @metamask/logging-controller is added as a direct dependency; TypeScript project references, README dependency graph, and CODEOWNERS for the init path are updated accordingly.

Integration is covered by unit tests on the init module and new Wallet tests for default state, constructor state.LoggingController, and routing LoggingController:add through the wallet messenger.

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