fix: surface release channel and update status in-app

[Adewumi99]

Overview

This PR surfaces release channel and OTA update status directly in the in-app settings status screen. Testers can now see which runtime version, update identifier, and channel they are running, manually check for newer updates, and copy a sanitized diagnostics block for bug reports.

Related Issue

Closes the Mobile release channel and update status issue.

Changes

📱 Status Screen Update

• [MODIFY] apps/mobile/app/settings/status.tsx
  • Displays runtime version, update identifier, and release channel from release metadata.
  • Adds an available-update indicator with a manual Check for Update action.
  • Adds a Copy diagnostics action that copies a bug-report-ready block.
  • Redacts wallet addresses and token IDs from the diagnostics block.
  • Falls back gracefully when no update metadata is present, such as in a development client.

🔖 Release Metadata Layer

• [MODIFY] apps/mobile/lib/release-metadata.ts
  • Exposes normalized runtime version, update identifier, channel, and update-available status.
  • Handles missing metadata and development-client scenarios with safe defaults.
  • Provides a sanitized diagnostics string that excludes wallet addresses and tokens.

Verification Results

npm run typecheck
✅ Typecheck passed

Manual device acceptance check:
✅ Status screen shows runtime version, update identifier, and channel
✅ Check for Update reports available update and refreshes status
✅ Copy diagnostics produces a bug-report block
✅ Dev client without update metadata renders fallback labels
✅ Diagnostics block contains no wallet addresses or tokens

Acceptance Criteria	Status
Status screen shows runtime version, update identifier, and channel	✅ Displayed in the settings status screen
Available update is indicated with a manual check-for-update action	✅ Update indicator + Check for Update button
Copy-diagnostics action produces a block suitable for bug reports	✅ Copy diagnostics generates sanitized block
Values degrade gracefully when running in a development client with no update metadata	✅ Safe fallbacks for missing metadata
Diagnostics block excludes wallet addresses and tokens	✅ Wallet/token data redacted before copy

Closes #1196

[drips-wave]

@Adewumi99 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[Cedarich]

Kindly fix CI

[Cedarich]

@Adewumi99

[Cedarich]

@Adewumi99