Lifei/configure key chain

[lifeizhou-ap]

What

• Goose configure

  • When environment variable for the key does not exist, user should add the key in the keychain
  • When environment variable for the key exists, user is asked to whether to add the key in the keychain. They can opt this out

• Goose session

  • When profile does not exist, exit with the user message to use "goose configure"
  • When key does not exist in the keychain or there is no environment variable, exit with the user message to use "goose configure"

**Screenshots

1. Configure when key does not found in environment variable or keyring

2. Configure when key has been in keyring, and the user does not update

3. Configure when key has been in keyring, and the user does not update

4. Configure when key only appears in environment variable, and ask customer to add it in the keyring. Customer opted out

5. Configure when key only appears in environment variable, and ask customer to add it in the keyring. Customer added it in the keyring

6. Start session when profile does not exists. Exit

7. Start session when key does not exists. Exit

[github-actions]

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:

No release type found in pull request title "Lifei/configure key chain". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

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