Implement Bypass Test Mechanism for Emergent Release

[musa-asad]

Description of the issue

When we release our operator and target allocator, we need to run the Build And Upload Artifact workflow in order to push the images to the release ECRs. However, sometimes we run into errors that block our release in our E2E tests that are expected to work.

We don't have a way to release when we have a test failure, which would be problematic under an emergent release.

Description of changes

• Added e2e-test-bypass-link and e2e-test-bypass-approver inputs to provide the failing E2E test link and the person who will 2PR the bypass.
• Added bypass-info job to display the e2e-test-bypass-link and e2e-test-bypass-approver inputs in the job summary.
• Added conditional to the e2e-test job to only run if both e2e-test-bypass-link and e2e-test-bypass-approver are empty.

Testing

Ran the following workflow in two situations:

gh workflow run build-and-upload-release.yml \
  --ref bypass-e2e-test \
  --field e2e-test-bypass-link=https://github.com/aws/amazon-cloudwatch-agent-operator/actions/runs/10255095727 \
  --field e2e-test-bypass-approver=musa-asad \
  --field release=false

Ran workflow: https://github.com/aws/amazon-cloudwatch-agent-operator/actions/runs/12182695411

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.