Multi-bridge Phase 2.8: Sentry/diagnostics enrichment with bridge name

[tashda]

Why

In multi-bridge mode, Sentry events and log lines must say which bridge they came from — otherwise debugging crash reports or connection failures is impossible.

What

• Sentry breadcrumbs and tags include the bridge name (a hashed/redacted display name; never the raw token, never the IP).
• Z2MWebSocketClient connection lifecycle logs include the bridge name as a structured field.
• Log lines emitted by AppStore+Events.swift etc. include bridgeID or display name.

Files

• Shellbee/Core/CrashReporting/ — Sentry setup, breadcrumb helpers.
• Shellbee/Core/Log/ — log formatter additions.
• Shellbee/Core/Networking/Z2MWebSocketClient.swift — log connection state changes with bridge name.

Verification

• Trigger a forced disconnect on bridge "Lab" via test center; confirm the Sentry event (in dev/staging) is tagged with bridge name "Lab".
• Confirm tokens are never included in Sentry payloads.

Phase

Phase 2 of multi-bridge support. Depends on #2.1.

[tashda]

Implemented in 78ae5d9 (Sentry breadcrumbs include bridge name).