Session initiated through OIDC shall not exceed OIDC session lifetime

### Current Behavior:

Without using DT logout feature, DT session remains active forever, irrelevant of SSO session lifetime.

### Prerequisite:

- OpenID Provider (OP) is configured with limited session duration (Likely the case when following [KeyCloak example](https://docs.dependencytrack.org/getting-started/openidconnect-configuration/) using a standard KC instance)

### Steps to Reproduce:

1. User connects to DT through OIDC
2. User stops using DT for longer than the SSO session duration (irrelevant if browser is closed or not)
3. User eventually returns to DT

-> User can continue to use DT without having to reauthenticate

### Expected Behavior:

User is redirected to login screen once its SSO session has expired (based on time solely here, see #2016 for additional improvement).

From a technical standpoint, considering implementing:
- Either:
- DT token expiration <= SSO token expiration [assuming SSO token duration can be retrieved]
- Configurable max age for DT token [otherwise]
- Automatic return to login screen once DT token has expired