Implement robust token refresh interceptor in client package

[Cjay-Cyber-2]

Description — what to implement and the why/impact.

Implement a token refresh interceptor in @astroid/client to seamlessly handle expired JWT tokens during API requests, preventing premature request failures for autonomous agents and developer applications.

Context & Requirements — background, constraints, design references, edge cases;

Background: Long-running AI agents make frequent API calls to Astroid. When tokens expire mid-session, requests fail unless an interceptor catches 401 Unauthorized responses, attempts a token refresh using stored credentials, and retries the original request once.
Constraints: Must prevent infinite loops during failed refresh cycles and safely queue concurrent requests while a refresh is in progress.

Acceptance Criteria — a checklist ("- [ ] ...") of specific, testable conditions that define "done".

• Interceptor catches HTTP 401 responses in @astroid/client
• Automatically attempts token renewal via auth client
• Retries original requests upon successful token refresh
• Queues concurrent requests during an active refresh
• Unit tests cover successful refresh and retry as well as failed refresh scenarios

Implementation Guidance — likely files/modules to touch (use real paths from the repo context)

Touch packages/client/src/ files handling HTTP requests and fetch wrappers. Follow existing error handling and client structure.

Testing & Validation — how the contributor should prove it works

Run pnpm test inside packages/client and ensure unit tests mock 401 responses and verify successful request retries.

Submission Guidelines — must open a PR that includes "Closes #"; assignment is required before starting.

---

Wave complexity: Medium