## What happened

When opening the LiteLLM admin UI at `/ui/login` on v1.88.0, the frontend loads the Next.js admin app and immediately calls several protected admin endpoints before the user is authenticated.

Those calls return 401 `ProxyException` responses, which is expected from an auth perspective, but they are also exported through OpenTelemetry/Langfuse as error traces. This creates noisy observability data simply from opening the login page.

Using `/fallback/login` avoids those calls, but it is not a good replacement for the normal UI login because it does not preserve the already-authenticated UI experience and asks the user to log in again.

## Expected behavior

Opening `/ui/login` should not generate observable backend error traces before the user submits credentials.

Possible fixes could be:

- avoid calling protected admin endpoints until the user is authenticated - treat expected pre-auth UI bootstrap 401s as non-error/noise for tracing - have `/ui/login` use a lightweight login-only page before loading authenticated admin data

## Actual behavior

Opening `/ui/login` triggers multiple unauthenticated requests such as:

- `/team/list` - `/models` - `/organization/…