When token expired and login performed, link used to navigate to Nomad is 'lost' and you are not redirected to your original destination.

### Nomad version
Output from `nomad version`

```
Nomad v1.6.2
BuildDate 2023-09-13T16:47:25Z
Revision 73e372ad94033db2ceaf53468b270a31544c23fd
```

### Issue

If you navigate to a specific link on the Nomad UI, example: https://my-nomad/ui/jobs/my-job@default
and you use OIDC logins, token expired, and you need to re-login, after re-login you won't be redirected back to https://my-nomad/ui/jobs/my-job@default but need to find your entry-link (or click through the nomad-UI) to get where you wanted to be.

It would be more convenient if Nomad would just handle login, and help you get back to where you wanted to go, instead of sticking to the login page and show you your token information.
 
### Reproduction steps
- use OIDC login, perhaps with a very low TTL
- wait for token expiry
- use a specific link like https://my-nomad/ui/jobs/my-job@default to something on nomad-ui
- re-login

#### Expected Result
- you would be redirected back to https://my-nomad/ui/jobs/my-job@default which was the original entry-page.

#### Actual Result
- you will not be redirected back to https://my-nomad/ui/jobs/my-job@default but are stuck on Authorization page, showing your token info.

Reproduce the expired-token flow using the Nomad UI link shown in the report, such as /ui/jobs/my-job@default, with OIDC and a short token TTL. Trace the authorization page and post-login redirect, then verify that re-login returns to the original UI destination rather than leaving the user on the token information page.

Written by the indexing model from the issue text.