Authorization Flow OAuth 2.0, logs in when switching APIs Everytime

## Bug description

When using Azure AD as an OAuth2.0 flow, swapping between operations initiates a login. This is nice because it does retrieve a new token, but can be a bit excessive if you are swapping between API calls. Is there a way to cache bearer token between operation calls?

## Reproduction steps

1. Configure Azure AD OAuth 2.0 flow
2. Navigate to desired API
3. Navigate to desired operation
4. Select Authorization Flow for Authorization Code or PKCE
5. Login
6. Swap to another API
7. Select Authorization Code
8. Login

## Expected behavior

Either silent auth, or cache token

## Is self-hosted portal?

No

## API Management service name

apim-qmt-ptfm-dev

## Environment

- Operating system: Windows
- Browser: Edge

Reproduce the flow by configuring Azure AD OAuth 2.0, logging in for one operation, and switching to another API and operation using Authorization Code or PKCE. Compare whether silent authentication or bearer-token reuse is possible across operation calls, and consider the issue complete when switching APIs no longer requires an unnecessary login while token retrieval remains valid.

Written by the indexing model from the issue text.