fix redudant login prompt from eozilla app

[TejasMorbagal]

added _effective_auth_type(): when a client config has auth_type="login" and already holds a resolved token (which is always true by the time show_app() runs), it's forwarded to the GUI as auth_type="token" instead of "login". The GUI's authType: "token" path just attaches the existing bearer token; "login" was making it discard that token and force a fresh interactive OAuth2/PKCE redirect.

Checklist (strike out non-applicable):

• Changes documented in CHANGES.md
  * [ ] Related issue exists and is referred to in the PR description and CHANGES.md
  * [ ] Added docstrings and API docs for any new/modified user-facing classes and functions
  * [ ] Changes/features documented in docs/*
• Unit-tests adapted/added for changes/features
• Test coverage remains or increases (target 100%)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[freds-dev]

LGTM!
Steps I did to verify:

• Authenticating to the S2GOS Keycloak token endpoint with cuiman configure, using auth_type: login and client ID: cuiman.
• Saving the resulting access token in a temporary local config.
• Launching the app with that config via cuiman show-app.
• Confirming the app connected to S2GOS immediately, without redirecting to Keycloak or prompting you to log in again.

Just one thing: After the token expired there is no refresh so the token won't work anymore and the requests return Jwt is expired.

[TejasMorbagal]

LGTM! Steps I did to verify:

* Authenticating to the S2GOS Keycloak token endpoint with `cuiman configure`, using `auth_type: login` and `client ID: cuiman`.

* Saving the resulting access token in a temporary local config.

* Launching the app with that config via `cuiman show-app`.

* Confirming the app connected to S2GOS immediately, without redirecting to Keycloak or prompting you to log in again.

Just one thing: After the token expired there is no refresh so the token won't work anymore and the requests return Jwt is expired.

Yes, refresh token won't work. The user has to re-login.