Modify the incoming request auth header to use the new bearer token

[JPinkney]

What does this PR do?

Currently, when a request is made and the token is refreshed through the interceptors the incoming request token isn't modified, leading to issues like eclipse-che/che#18311 (comment). This PR makes sure that the incoming request token is updated when the keycloak token is updated

Which issue is this PR related to?

eclipse-che/che#18311

Signed-off-by: Josh Pinkney joshpinkney@gmail.com

[che-bot]

❌ E2E dashboard-next tests failed ❗

See Details

• Jenkins job

• test report

• logs and configs

• Che dashboard-next image:docker.io/maxura/che-dashboard:110

• Che server image: docker.io/maxura/che-server:110

Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)

• Use comment "[dashboard-next-ci-test]" to rerun the 'dashboard-next' e2e tests

[sleshchenko]

Tested and it fixes the issue with using expired access token for http requests.

But it does not solve the issue with websockets. Steps to reproduce:

1. Open Dashboard.
2. Wait until token is expired, use https://jwt.io/#debugger-io to check what is the time.
3. Do any operation on the dashboard, like create a workspace from sample. Token is refreshed and used:tada:
4. Do

oc patch deployment/che \
        --patch "{\"spec\":{\"replicas\":1}}
oc patch deployment/che \
        --patch "{\"spec\":{\"replicas\":0}}

5. Check that Dashboard uses the expired token to establish websocket connection

But it must not block the current PR since it's a dedicated piece in the area of Workspace Client https://github.com/che-incubator/che-dashboard-next/blob/master/src/services/cheWorkspaceClient/index.ts#L135

[JPinkney]

I'm going to merge this PR and then introduce the changes for the WebSockets issue in another PR

[che-bot]

❌ E2E dashboard-next tests failed ❗

See Details

• Jenkins job

• test report

• logs and configs

• Che dashboard-next image:docker.io/maxura/che-dashboard:110

• Che server image: docker.io/maxura/che-server:110

Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)

• Use comment "[dashboard-next-ci-test]" to rerun the 'dashboard-next' e2e tests