chore: deploy to production became optional with choice for the image_tag

[geekbrother]

Description

This PR changes the release and cd GitHub Actions workflows to the following:

Release:

• Adding user inputs for the release for options to deploy to staging and/or prod environments after the release is made.

CD:

• Making deployment to the staging and prod optional for the cd workflow by adding the ability to choose to which environment the image should be deployed when cd is invoked.
• Adding image_tag string input for the cd to make the ability to choose which image version/tag from ECR should be deployed. The default blank input value is the latest release version/tag. This adds an ability to test staging releases by deploying into staging only and falls back to the previous version in case we need to roll it back without making a revert commit and make another release.

Resolves #224

How Has This Been Tested?

Tested by the GitHub Actions VSCode plugin by checking validations.
Smoke testing in a forked repo.
Should be tested when merged as well.

Due Diligence

• Breaking change
• Requires a documentation update
• Requires a e2e/integration test update

[geekbrother]

We don't need this anymore, because we can get the latest release version from the input image_tag when calling from the release, or it's getting by the terraform itself when passing an empty one.

[xav]

I'm approving if this is blocking you, otherwise, I'm not sure about latest since versioned tags haven't really been a problem and a generic one can be tricky sometimes.
Anyway, this will be overwritten with the migration.

[geekbrother]

Anyway, this will be overwritten with the migration.

@xav do you mean by migration of the future updates of the CD workflow to make it consistent across all services?
The reason for these changes is to control what version we are shipping to prod and distinguish to which environment to ship. At the moment it's kind of messy.