feat: TUI for configuring cli profiles

[jsibbison-square]

More to be done but decent progress

The config is growing and becoming more complicated so this PR is exploring alternative UX for managing config. Specifically using a TUI to manage the profiles.

Experiemental so currently accessed via goose e-configure

Navigation

• [x] Profiles
• [x] Providers
• [ ] Systems

Profiles

• [x] list profiles
• [x] rename profile
• [x] view profile details
• [x] edit profile details
  • [ ] profile field validations
• [x] add profile
• [ ] remove profile
• [ ] systems

Providers

• [x] list providers
• [x] list provider configuration key names
• [x] show provider configuration completion state (are all env or keyring variables set)
• [ ] configure provider
• [x] test provider connection (recommended model)
  • [ ] test provider connection with custom model

[github-actions[bot]]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

Unknown release type "WIP" found in pull request title "WIP: TUI for configuring cli profiles". 

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[baxen]

Going to close this for now as it is behind a few refactors. However still think the idea is great and we should revisit