feat(aws): add sso

[hans-d]

Standards checklist:

• The PR title is descriptive.
• The PR doesn't replicate another PR which is already open.
• I have read the contribution guide and followed all the instructions.
• The code follows the code style guide detailed in the wiki.
• The code is mine or it's from somewhere with an MIT-compatible license.
• The code is efficient, to the best of my ability, and does not waste computer resources.
• The code is stable and I have tested it myself, to the best of my abilities.

[ohmyzsh]

Bleep bloop. I determined that these users own the modified files: @maksyms.

[ketiko]

+1

[larson-carter]

I would like an explanation of the reasoning on how it would handle the actual authorization process? Is it 100% token based and will they ever expire?

[hans-d]

Authorization is done completely via the sso flow:

• if token is not valid anymore (checked by doing a simple call), it will request a new token. Normally this involves displaying a URL you have to visit and enter some code, which in most cases can be opened automatically in a browser. As a user you still have to confirm the request
• if token is valid at the time of change, it will continue to use it

if the token becomes invalid/expired, one has to either do aws sso login or "switch" to the same profile. Expiration is tied to the sso settings within aws. (in my cases, sessions get expired)