feat: saved api_key to keychain for user

[lifeizhou-ap]

Why Enable users to store api key in keychain for convenience

What

Rules When the api key environment variable does not exist,

• it looks up the api key from keychain. if it does not exist, then
• the users are prompted to enter the api key and
• the users are prompted whether they want to save the api key in the keychain

Changes

• Implemented rules as above
• Extract create_exchange into a util file
• Moved SessionNotifier to a separate file

[lamchau]

very cool! how would a user update the keychain with the same prompts (typo, rotation, etc)?

just had a thought! what do you think of a goose config (and maybe even a goose check)? that way we can use it as a catch all to do things

• check latest version
• check profiles
• check api keys of each providers (both environment variables and keychain)?

[michaelneale]

cc @alecthomas

[lifeizhou-ap]

just had a thought! what do you think of a goose config (and maybe even a goose check)? that way we can use it as a catch all to do things

• check latest version
• check profiles
• check api keys of each providers (both environment variables and keychain)?

Yes, that could be useful.

[lifeizhou-ap]

how would a user update the keychain with the same prompts (typo, rotation, etc)?

I think we can enhance this later. When we load the api key from keychain, the console prints the message about the api_key source. If it is not correct, the user still can update by themselves.

[alecthomas]

This is awesome!