Ability to generate cloud credentials in the CLI build tool

[radeusgd]

Pull Request Description

I needed to generate credentials for the staging environment.
The standard workflow to do this was to rebuild the IDE with a different .env file. However this took so long, as it was finishing (and the build failed for me), I was already finishing this script.

This should be useful for testing cloud integration from the CLI during development. It relies on the same logic as is used for generating credentials in our CI tests.

Important Notes

Usage:

• You need to set up the same set of environment variables as for the CI workflow:
  • ENSO_CLOUD_COGNITO_REGION, ENSO_CLOUD_COGNITO_USER_POOL_ID, ENSO_CLOUD_COGNITO_USER_POOL_WEB_CLIENT_ID - which can be taken from the .env file corresponding to a given environment, although there they have slightly different prefixes (as the config is for IDE not CI).
  • ENSO_CLOUD_TEST_ACCOUNT_USERNAME and ENSO_CLOUD_TEST_ACCOUNT_PASSWORD
• Then running ./run backend generate-cloud-credentials should create a enso.credentials file in your CWD. To make our libs use it, you can set ENSO_CLOUD_CREDENTIALS_FILE env var to point at it.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  TypeScript,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• Unit tests have been written where possible.
• If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
  or the Snowflake database integration, a run of the Extra Tests has been scheduled.
  • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

[Akirathan]

What kind of expiration will the generated credential file have? I know that when I am running IDE in staging env, the $HOME/.enso/credentials file is changed every time I launch the app. Could you point the ./run backend generate-cloud-credentials to take the staging environment variables by default?