Fix/reactive auth sharing persist

[gitmibrahim]

What

1. Shared Reactive Auth State (packages/core/src/runtime/auth.ts):

   • Centralized authentication storage using a per-spec ref cache (authStoresCache and getAuthStore).
   • Cleaned up the unused onMounted import.
   • Added unit tests in auth.spec.ts to verify state sharing across multiple hook instances.

2. Immediate Credential Persistence (packages/core/src/components/AuthControls.vue):

   • Added @input="commit" handling on the credential input field to persist modifications instantly.
   • Added unit tests in AuthControls.spec.ts confirming immediate persistence on input events.

3. Request Authorization Tests (packages/core/src/components/EndpointTryPanel.spec.ts):

   • Created a new spec suite covering token/auth injection into the Request Envelope for:
     • bearer
     • oauth2
     • basic
     • apikey (header, query, and cookie locations)

Why

Closes #46

• Cross-Component Reactivity: Previously, each instance of the useAuthState hook maintained its own independent state. If multiple playground or auth control components were active for the same spec, a credential update in one would not reactively propagate to others in real-time. Shared caching ensures perfect UI synchronization.
• Improved UX in Playgrounds: Persisting credentials on keypress (input) ensures that API try-it requests and code snippets are dynamically updated without forcing the user to press Enter or trigger a blur event by clicking elsewhere first.
• Improved Test Coverage: Verified that all standard OpenAPI security schemes are successfully injected into outgoing playground requests, preventing future regressions.

How to test

• npm run typecheck passes
• npm run test:run passes
• Manually verified in npm run dev

[gitmibrahim]

@rodindev Just a quick reminder to request a review on this PR when you're ready so we can get it processed. Thanks!

[rodindev]

Thanks for this. The shared Map<specName, Ref> is the right approach. I synced your branch with main (1.8.0 is out) and CI is green. Left a few inline notes, the watch one is the only blocker.

[rodindev]

Thanks! The previous comments are all addressed nicely.

CI is red though, AuthControls.spec.ts fails on the “clears stored credentials” test.

Sould be a small fix – almost there 🙂

[gitmibrahim]

@rodindev Thanks for the review. Is there still a blocker here?