Feat/privacy posture chip 152

[Adedoyinjr]

Summary

• add a header-level PrivacyPostureChip distinct from the per-scan PrivacyBadge
• show strict posture only when telemetry is off and the active chain’s RPC routes are non-default
• list the configured RPC hosts with copy controls
• expose telemetry state and link to /privacy
• update posture immediately when telemetry consent changes
• support keyboard interaction, Escape handling, outside-click dismissal, and unique disclosure IDs
• keep all posture derivation local without making network requests or sending RPC data to telemetry
• document and expose telemetry controls on the privacy page

Testing

• Added privacy posture derivation tests
• Added telemetry consent subscription and storage-event tests
• pnpm install --frozen-lockfile passed
• pnpm format:check passed
• pnpm build passed
• pnpm test:unit passed

Fixes #152

[drips-wave]

@Adedoyinjr 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

[vercel]

@Adedoyinjr is attempting to deploy a commit to the truthixify's projects Team on Vercel.

A member of the Team first needs to authorize it.

[truthixify]

Merged. Reads local config only and stays clear of the existing per-scan PrivacyBadge, which is the distinction I was worried about when I wrote the issue. Thanks @Adedoyinjr.