fix(clerk-js): Set __session and __client_uat before invalidating cache

[nikosdouvlis]

Description

Fixes the following flow that mainly affected nextjs apps:

Setup:

• Dev instance
• Latest next, clerk/nextjs and clerk-js
• Multi-app-same-domain FF disabled
  Steps:
• Go to app
• Enter email and hit continue (signIn.create): client_uat is 0
• Enter password and hit continue (signIn.attemptFirstFactor) : client_uat > 0 (for accounts)
• Clerk-js invalidates cache : client_uat is 0 because clerk-js does not set it correctlly

The main issue in the clerk-js codebase was that during sign-in/sign-up, we set the cookies implicitly when we update the current Client resource (Base -> updateClient -> Client.fromJson() -> new Session -> hydrate token cache). However, the Clerk.client only gets updated AFTER the token cache is hydrated, so setting the client_uat token failed because when it runs, Clerk.client.activeSessions is still 0 (its still the previous value)

Checklist

• npm test runs as expected.
• npm run build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

[changeset-bot]

🦋 Changeset detected

Latest commit: 55f46af

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

Name	Type
@clerk/clerk-js	Patch
@clerk/astro	Patch
@clerk/chrome-extension	Patch
@clerk/clerk-expo	Patch

Not sure what this means? Click here to learn what changesets are.

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