Switch protocol dashboard to OAuth 2.0 write scope + image mirrors

[raymondjacobson]

Summary

• OAuth 2.0 migration: Replace deprecated write_once scope with standard write scope for the Connect Audius Profile flow. Rewrites useConnectAudiusProfile hook to construct OAuth URL manually with PKCE, sign wallet signatures with ethers (instead of audiusLibs.web3Manager), and exchange auth codes for tokens after the popup completes. Removes all references to old SDK OAuth APIs (oauth.init, getCsrfToken, activePopupWindow, OAUTH_URL).
• Web app OAuth page: Extends write scope to support tx=connect_dashboard_wallet / tx=disconnect_dashboard_wallet params, reusing existing handleAuthorizeConnectDashboardWallet / handleAuthorizeDisconnectDashboardWallet handlers.
• Image mirror support: Adds MirrorImage component with 3-second per-URL timeout fallback for profile pictures and trending artwork. Replaces raw <img> tags and backgroundImage inline styles that would stall on unresponsive content nodes.

Test plan

• Connect Audius Profile: click button → popup opens → authenticate → profile picture + name appear
• Disconnect Audius Profile: click Unlink → popup opens → authenticate → profile removed
• Profile pictures load with mirror fallback (simulate slow node by throttling network)
• Trending tracks/playlists/albums artwork loads correctly with mirror fallback
• Wallet connection via Web3Modal still works (no regression)
• npm run verify passes in protocol-dashboard

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1d340d6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
27814482	Triggered	Generic High Entropy Secret	1d340d6	packages/protocol-dashboard/src/services/Audius/sdk.ts	View secret
27814482	Triggered	Generic High Entropy Secret	1d340d6	packages/protocol-dashboard/src/hooks/useConnectAudiusProfile.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[github-actions]

🌐 Web preview ready

Preview URL: https://audius-web-preview-pr-14052.audius.workers.dev

Unique preview for this PR (deployed from this branch).
Workflow run