UI Forwarding Expired Tokens to Codec Server

Describe the bug
Temporal UI is setup with a codec server and to forward the user access token the ui has. It seems that temporal has a token with a pretty short lifespan. When the token is forwarded to our codec server, and then that codec server validates it with the issuer, it receives the error that the token has expired.

To Reproduce

1. Setup Temporal Web With OIDC (were using v2.21.3)
2. Setup Codec Server With OIDC validation against the issuer
3. Log into Temporal web.
4. Validate that the new token does work and decodes workflows.
5. Wait for token to expire (aprox 30min)
6. Note that temporal web does not request a new login.
7. Try to view an encoded workflow.
8. Note errors.
9. Manually hit the log out button in web ui.
10. Refresh page.
11. Note decoding is now working.

Expected behavior
For temporal to get a new valid token and forward that to the codec server when needed.

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]
  Windows 11
• Browser [e.g. chrome, safari]
  Chrome 120
• Version [e.g. 22]

Additional context
Okta is the issuer we use.

Trace the UI's OIDC token lifecycle and the request path that forwards credentials to the codec server. Reproduce the failure after the approximately 30-minute token lifetime, then verify that viewing an encoded workflow continues to work without manually logging out and back in.