feat(experiment): use charm prompt with login

[zimeg]

Summary

This PR uses charm prompts with the login command! 🍀

Preview

Before changes

before.mov

After changes

after.mov

Reviewers

Build the changes of this branch and confirm the following:

$ slack login           # No experiment has an unchanged experience
$ slack login -e charm  # Attempt login with charm prompts
$ slack login -e charm  # Attempt interrupting the prompts

Requirements

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[zimeg]

📝 A few notes for the reviewers! I'm interested in following up with improved testing strategies, but for now let's keep experimental changes gated to find edges in implementation I think!

[zimeg]

🗣️ note: We might want to reconsider how we handle interrupted prompts, but for now I find this suitable at capturing these errors to match current behaviors!

[zimeg]

🪓 thought: I'm hoping to nudge logic related to prompts closer toward cmd overall!

[srtaalej]

LGTM! so excited to get this out 💫 🚀

[zimeg]

@srtaalej Likewise, I'm pumped for these prompts! Let's merge this now so we can start building confidence in these changes 🧰 ✨

[codecov]

Codecov Report

❌ Patch coverage is 25.80645% with 23 lines in your changes missing coverage. Please review.
✅ Project coverage is 64.68%. Comparing base (4fb7b4f) to head (df12d15).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/pkg/auth/login.go	0.00%	23 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #349      +/-   ##
==========================================
- Coverage   64.68%   64.68%   -0.01%     
==========================================
  Files         212      212              
  Lines       17805    17820      +15     
==========================================
+ Hits        11518    11527       +9     
- Misses       5209     5219      +10     
+ Partials     1078     1074       -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[meowgorithm]

Hey! I'm from the Charm team. @srtaalej and @zimeg, is there anything we can do to help with this? We'd be happy to open an (ahem) Slack Connect channel for comms.

[zimeg]

@meowgorithm Hello! 🍀😸 Thank you so much for asking! The examples y'all share are great inspiration but we might need a few pointers more-

Our current approach to prompting matches flag options before asking for interactive inputs most of the time. It's been alright in testing if the CLI works for scripting purposes, but unit testing has led us to stubbing mocks across an interface as:

slack-cli/cmd/project/create_test.go

Lines 49 to 56 in 62770ba

	cm.IO.On("SelectPrompt", mock.Anything, "Select an app:", mock.Anything, mock.Anything).
	Return(
	iostreams.SelectPromptResponse{
	Prompt: true,
	Index: 0,
	},
	nil,
	)

A quick approach of #350 tries to continue this pattern, but I'm most curious to best practices otherwise!

Would inlining forms be better for testing and customizations overall? I realize too that a channel might be best for these ramblings... Will look for a link soon! 🌚