Refresh session performance 1: Waiting for response from the server.

[alextok]

DBSC performs well during active use of the web app but struggles when the device or web app has been idle for a while.

If the device has been unused or a browser tab inactive, the auth cookies will expire. Before allowing workload requests, the cookie needs to be updated. This requires the client to wait for a network call to the session refresh endpoint before workload navigation can proceed. Therefore, there are two requests:

1. Session refresh request.
2. Wait for response.
3. Workload request.

We can address this problem by including a special header in the request with refresh session information. There could be alternative approaches.

Similar issue discussed here: #12