Create Github Action to validate PR Test success

[TravisStark]

Description of the issue

To require integration test success prior to PR merge, we need to add a required status check that only passes if the test workflow completes.

Note: Investigated blocking PR merge based on a workflow success using rulesets is only available to Github Enterprise accounts
https://docs.github.com/en/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets#require-workflows-to-pass-before-merging

Description of changes

Create new jobs on the PR Build and PR Test workflows to validate prior job success on workflow completion.

• Verify All PR Test Jobs
• Verify All PR Build Jobs

The Verify All PR Test Jobs action will be added to the required status checks in the branch protection settings after this PR is merged and the job runs successfully.

Added BuildAndUpload as a required dependency of the EC2SELinuxIntegrationTest job

License

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

Tests

Validated on this PR

https://github.com/aws/amazon-cloudwatch-agent/actions/runs/15494936344/job/43630356781?pr=1715

Job output for Verify All PR Build Jobs (PR Tests are not passing consistently currently)

Successfully validated jobs:
test-data-race
build
changes
lint

All required jobs completed without failures!

Sample failing case:

Successfully validated jobs:
BuildAndUpload
CheckLabel
EC2SELinuxIntegrationTest
GenerateTestMatrix
OutputEnvVariables
StartLocalStack
StopLocalStack

Failed jobs:
EC2LinuxIntegrationTest

Requirements

Before commit the code, please do the following steps.

1. Run make fmt and make fmt-sh
2. Run make lint

[agarakan]

Can this be changed into a for loop to make it reusable? It seems like the rest of the validation is identical here and in the other file

[TravisStark]

I'll try that out.

[agarakan]

All comments minor, logic looks good. approved

[agarakan]

Looks clean, maybe a future iteration can be about consolidating these into a common function that both workflows invoke.