[ENHANCEMENT] Allow dynamic selection of authentication provider in percli

[celian-garcia]

Description

This PR clarifies the current support of different authentication providers by percli. It removes any doubt with clear messages on what we can do and cannot and it starts the implementation with a simple selector.

Screenshots

When backend support several auth provider. The command line ask you to select

... with an error message for the moment for OIDC/OAuth 2.0, as it is not supported by the CLI

When the backend does not support native, we cannot set username or password arguments

One can set the provider through argument (it might be useful when we'll implement the client credentials flow)

Checklist

• Pull request has a descriptive title and context useful to a reviewer.
• Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
  following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
• All commits have DCO signoffs.

UI Changes

• Changes that impact the UI include screenshots and/or screencasts of the relevant changes.
• Code follows the UI guidelines.
• Visual tests are stable and unlikely to be flaky.
  See Storybook
  and e2e docs for more details. Common issues
  include:
  • Is the data inconsistent? You need to mock API requests.
  • Does the time change? You need to use consistent time values or mock time utilities.
  • Does it have loading states? You need to wait for loading to complete.