CLOUDP-330675: Reworks atlas auth login flow

[cveticm]

Proposed changes

1. Adds prompt flow to ask user which form of authentication they would like to log in with.

atlas auth login
? Select authentication type:  [Use arrows to move, type to filter]
> UserAccount - (best for getting started)
  APIKeys - (for existing automations)

APIKeys logic is taken directly from atlas config init. This duplicated code will be removed as a part of CLOUDP-329797

2. Adds hidden flag --force. When used, browser flow (User Account) is taken and user will not be prompted on authentication method.

Jira ticket: CLOUDP-330675

Checklist

• I have signed the MongoDB CLA
• I have added tests that prove my fix is effective or that my feature works
• I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
• I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
• I have updated test/README.md (if an e2e test has been added)
• I have run make fmt and formatted my code

[github-actions]

APIx Bot : a message has been sent to Docs Slack channel 🚀.

[jwilliams-mongo]

if this is true, will the CLI use only config files / env variables for auth? Or perhaps a session that is already authenticated? Wondering if we need to be clear about that behavior here.

I think we can remove the word "try" as it isn't clear to me if this is true if it just doesn't open a browser window or if it opens it if specific conditions are met or not met.

Suggested change

	cmd.Flags().BoolVar(&opts.NoBrowser, "noBrowser", false, "Don't try to open a browser session to authenticate your User Account.")
	cmd.Flags().BoolVar(&opts.NoBrowser, "noBrowser", false, "Don't open a browser session to authenticate your User Account.")

[cveticm]

When --noBrowser=false, a browser session is opened for users to authenticate through.

When it is true, the behaviour is that a browser session will not be opened automatically and users will have to access the link manually.

Would this make that behaviour more clear?

Suggested change

	cmd.Flags().BoolVar(&opts.NoBrowser, "noBrowser", false, "Don't try to open a browser session to authenticate your User Account.")
	cmd.Flags().BoolVar(&opts.NoBrowser, "noBrowser", false, "Don't automatically open a browser session.")

[fmenezes]

make sure to run by Jonny, he designed these changes

[cveticm]

Noted, will check

[cveticm]

modified this logic to more closely follow what was outlined in Scope (prompt user to press a key to open browser) and checked w Jonny, he gives his thumbs up on new implementation

[github-actions]

Coverage Report 📈

Branch	Commit	Coverage
SA_refactor_feature_branch	e82d6b3	25.7%
CLOUDP-330675_atlas_auth_login_flow	626e423	25.8%
	Difference	.1%

[fmenezes]

while I think this is fine, why have you added this? don't we just disable telemetry on our tests?

[cveticm]

I tried and was unable to get this to work for testing runApiKeysLogin.
I believe the limitation is that, even if telemetry is disabled, the prompts are still asked and wait for input, resulting in the test failing with err EOF.

This structure also allows us to mock prompt responses (as seen for Test_shouldRetryAuthenticate here) which would allow us to cover more specific cases in future if needed.