Make relay helpers more idiomatic Effect

[cursor]

What Changed

• Replaced the shared relay JWT Data.TaggedError with granular Schema.TaggedErrorClass sign/verify errors and a RelayJwtError schema union.
• Added direct relay JWT tests using @effect/vitest with assert.
• Replaced the managed relay environment-status atom key's raw JSON.parse/JSON.stringify path with a Schema.fromJsonString codec backed by the existing relay contract schema.
• Added a cache-key regression test for equivalent environment inputs with different object insertion order.

Why

These are focused idiomatic Effect improvements: structured serializable errors for auth primitives, schema-backed JSON parsing/encoding instead of ad-hoc record casts, and tests that exercise the behavior without module-level mocks.

Validation:

• bun run test src/relayJwt.test.ts from packages/shared (3 tests passed)
• bun run test src/managedRelayState.test.ts from packages/client-runtime (5 tests passed)
• pnpm exec vp check (passed with pre-existing root package.json diff temporarily stashed)
• pnpm exec vp run typecheck (passed with same pre-existing root package.json diff temporarily stashed)

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (not applicable: no UI changes)
• I included a video for animation/interaction changes (not applicable: no UI changes)

  

Note

Replace generic relay JWT errors with structured RelayJwtSignError and RelayJwtVerifyError classes

• Replaces the generic RelayJwtError in relayJwt.ts with two Schema.TaggedErrorClass types: RelayJwtSignError (carries typ, cause) and RelayJwtVerifyError (carries typ, issuer, audience, cause).
• Changes statusKey in managedRelayState.ts to use schema-encoded keys instead of JSON.stringify, so logically equivalent environment objects with different property order map to the same cache entry.
• Adds parseStatusKey schema validation so only conforming keys are accepted.
• Behavioral Change: callers catching relay JWT errors must now handle the new tagged error types instead of the previous RelayJwtError.

^{Macroscope summarized cbc057a.}

[github-actions]

🚀 Expo continuous deployment is ready!

• Project → t3-code
• Platforms → android, ios
• Scheme → t3code-preview

	🤖 Android	🍎 iOS
Fingerprint	ae17d94b35f91f9c608a63dadbc3ddd9f4ba056e	313e506a7f15a9c3f15b01d787d68a12382432bf
Build Details	Build Permalink Details Distribution: INTERNAL Build profile: preview:dev Runtime version: ae17d94b35f91f9c608a63dadbc3ddd9f4ba056e App version: 0.1.0 Git commit: 5c7ed5d7b514e3deedad7b0b0810c4cb9fb0f6a7	Build Permalink Details Distribution: INTERNAL Build profile: preview:dev Runtime version: 313e506a7f15a9c3f15b01d787d68a12382432bf App version: 0.1.0 Git commit: 5c7ed5d7b514e3deedad7b0b0810c4cb9fb0f6a7
Update Details	Update Permalink Details Branch: pr-3000 Runtime version: ae17d94b35f91f9c608a63dadbc3ddd9f4ba056e Git commit: 5c7ed5d7b514e3deedad7b0b0810c4cb9fb0f6a7	Update Permalink Details Branch: pr-3000 Runtime version: 313e506a7f15a9c3f15b01d787d68a12382432bf Git commit: 5c7ed5d7b514e3deedad7b0b0810c4cb9fb0f6a7
Update QR