Web: Redirect to login upon missing session cookie

[kimlisa]

fixes #20996

Why: We use non-persistent (session) cookie. When you close a browser, session cookies get cleared from the browser. Then when you re-open browser, load the teleport app, try to make a teleport api call to a protected endpoint WithAuth, it fails to authn because a cookie wasn't sent with the request.

There is three kind of dialogue shown depending on which webapp route you take.

AppLauncher component catches error (from trying to getFqdn)

Reproduce (chrome, but works on any browser):

1. login to teleport and successfully launch an app
2. close the browser
3. reopen browser and launch the app (copy and paste app URL)

Enterprise: the WaitingRoom catches error (from trying to getUserContext)

1. login to teleport
2. close the browser
3. reopen browser and go to some teleport URL

Open source: the root CatchError catches error (from trying to getUserPreferences)

Our component tree looks like this:

<CatchError> // our root error catcher if the childrens did not  handle it
  <Authenticated>  // <----- where we should be checking validity of cookie and session
    <AppLauncher/>
    <WaitingRoom>   // only in enterprise
        {... childrens subjected to waiting room}
    </WaitingRoom>
  </Authenticated>
</CatchError>

Prior to this PR, in the Authenticated layer we were only checking for valid session stored in local storage. But gives false positives. Now we just make the api call to the /status endpoint right away and fail earlier in the tree (instead of 15 seconds later from starting an interval timer that polls this endpoint)

All the above scenarios, the user will be redirected to the login right away. On rare occassions where the /status just fails to fetch, this is what the user will see:

[gzdunek]

LGTM, I left a few minor comments.

[gzdunek]

Suggested change

	<Text mb={3}>Try again by refreshing the browser.</Text>
	<Text mb={3}>Try again by refreshing the page.</Text>

[gzdunek]

ErrorDialog?

[gzdunek]

Suggested change

	const checkUserIsAuthenticated = async () => {
	const checkIfUserIsAuthenticated = async () => {

[gzdunek]

We can move it above try.

[gzdunek]

WDYT of showing an <Indicator /> during loading?

[gzdunek]

I'd shorten it a bit:

Suggested change

	* which just checks if the cookie sent from browser is valid and user
	* session is still valid.
	* which checks if the cookie and the user session are still valid.

[public-teleport-github-review-bot]

@kimlisa See the table below for backport results.

Branch	Result
branch/v13	Create PR
branch/v14	Create PR