Remove "In Memory" storage option and improve OIDC kubeconfig persistence

[mrCherry97]

Summary

The In Memory storage option does not provide real value and causes poor user experience, especially when using OIDC authentication. We should consider removing this option and improving kubeconfig persistence behavior.

Problem

When a user selects In Memory as the kubeconfig storage method and authenticates via OIDC:

• The page reloads after successful login
• All in-memory data is lost
• The kubeconfig disappears
• The user must re-upload or reconfigure the cluster every time

This behavior makes the In Memory option impractical and confusing for users. Since page reloads are expected in OIDC flows, losing critical configuration breaks the workflow.

Why this matters

• Breaks user sessions after authentication
• Creates unnecessary friction for OIDC users
• The option gives a false sense of persistence
• Leads to repeated setup steps and frustration

Proposed changes

• Remove the "In Memory" storage option from the UI
  • It does not support real-world usage patterns
  • It is incompatible with OIDC login flow

Expected outcome

• Users do not lose kubeconfig after authentication
• Storage options clearly communicate persistence behavior
• Improved UX for OIDC users
• Reduced support and confusion around lost configs

Additional context

This issue is consistently reproducible when:

• Using OIDC authentication
• Selecting In Memory storage
• Page reloads after login

Acceptance criteria

• "In Memory" option is removed OR redesigned
• Kubeconfig persists across OIDC login
• Clear documentation for storage behavior