Add `SENTRY_RELEASE` to the Docker image environment when built

[sarayourfriend]

Problem

@krysal pointed out that Sentry consumes some things automatically from the environment. SENTRY_ENVIRONMENT for example, which we set in the ECS task definition. SENTRY_RELEASE is another one and one we could easily set in the Docker image so that we get better problem timelines.

Description

Add the SENTRY_RELEASE environment variable to the image. You may need to add a build arg with which to populate the ENV call.

Implementation

• [ ] 🙋 I would be interested in implementing this feature.

[krysal]

More info from Sentry Documentation:

When you give Sentry information about your releases, you can:

• Determine issues and regressions introduced in a new release
• Predict which commit caused an issue and who is likely responsible
• Resolve issues by including the issue number in your commit message
• Receive email notifications when your code gets deployed

Additionally, releases are used for applying source maps to minified JavaScript to view original, untransformed source code.

The first part of the second point is particularly attractive. Would be great if is paired with the reactivation of the Sentry Release GitHub Action. I guess it will require updating the <environment>-frontend-deploy/action.yml files (generated by terraform).