INF-209 Trigger SDK releases by commit

[joaquincasares]

Description

Trigger SDK releases by commit instead of blindly using master.

Changes to existing flow:

• The release script now requires a GIT_TAG positional argument.
• The GIT_TAG must be found on a master or release* branch.
• The release script will fail if the user is not circleci.
• We no longer require the full_ci CircleCi Trigger parameter.
• full_ci will no longer trigger jobs, but expose hold-jobs.
• A string sdk_release_tag parameter is now used to immediately trigger an sdk release (no hold job, no re-triggering of all other jobs).

Additions:

• Release script now cleans up after failed attempts to deploy.
• Helper script is now included to send an API request to CircleCI to trigger the above job: .circleci/bin/deploy-sdk.sh
• Helper script pre-checks if GIT_TAG is on master before submitting API request.

Helper script:

$ .circleci/bin/deploy-sdk.sh -h
Usage: deploy-sdk.sh [OPTIONS]

Options:
  -h, --help                 Show this message and exit.
  -t, --git-tag TEXT         Git tag or commit to deploy from.  [required]
  -k, --circle-api-key TEXT  Used when $CIRCLE_API_KEY is not set.  [required]

Usage:

export CIRCLE_API_KEY=xxxx
.circleci/bin/deploy-sdk.sh -t $GIT_TAG

Tests

I will merge to master, run one deploy, and monitor the next few deployments to ensure they worked correctly.

Example runs:

$ .circleci/bin/deploy-sdk.sh -t a22fb55
Commit not found on master, nor release branches: remotes/origin/sdk-v0.0.21

$ .circleci/bin/deploy-sdk.sh -t 87c4f2c836ac3e60f3c9fc3a16df2a18de7d43b5
{'created_at': '2022-07-27T22:43:41.641Z',
 'id': 'f7219248-45be-4b44-b2ee-837b852d14e6',
 'number': 25655,
 'state': 'pending'}

https://app.circleci.com/pipelines/github/AudiusProject/audius-protocol/25655

Monitoring - How will this change be monitored? Are there sufficient logs / alerts?