test: Integrate automated smoke test into release workflow

[adebayor123]

Details

Currently as part of the release process, contributors in AWS RUM manually perform smoke tests to gain assurance on the newly-releasing web client version's behavior. This process has a couple of issues:

1. There are no predefined set of tests that contributors go through.
2. It is easy to miss out on regressions.

To mitigate this, this PR integrates automated smoke test as part of the release workflow.

Changes

1. Embed smoke.html into repository, with all sensitive parameters anonymized and stored in GitHub secrets.
2. During the release workflow, the automated smoke test will run after a new version has been pushed to the CDN.
3. The smoke test will perform a set of defined test cases on the new version of the web client.
4. If the smoke test cases are successful, proceeds to NPM release. Otherwise, stops the release workflow.

Testing

1. Successful Run: https://github.com/adebayor123/aws-rum-web/runs/6381491772?check_suite_focus=true
2. Unsuccessful Run: https://github.com/adebayor123/aws-rum-web/runs/6381538124?check_suite_focus=true
3. Final verification Run: https://github.com/adebayor123/aws-rum-web/runs/6381730545?check_suite_focus=true

Setup

This is only applicable to AWS RUM members.

Notes

When the test is run with 4 workers, all the ingested events were retrieved within a maximum of 2 minutes. However, when the tests are run with 6 workers, around 1-2 cases time out (5m) and the overall time to retrieve events is increased to 2-3 minutes.
AWS RUM team should investigate into this issue.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[qhanam]

question: Would it be difficult to version the smoke test file? E.g., smoke-1.5.1.html? This way we could (1) retain older versions for testing, and (2) it would be easy to verify which versions have been tested.

This isn't a blocker, but something to consider if it's easy to do.

[adebayor123]

In order to do so, I think the changes need to happen on (1) CDK to edit the bucket with versioning characteristics (2) upload_smoke_test.sh and cd.yaml.

I think it's better to have the fix incorporated with this, since otherwise we will have to keep the enhancement in our backlog (which might get overlooked).

I will add the changes with the next revision.

[adebayor123]

Clarification: Bucket versioning is not needed - we expect the bucket to hold different versions of the smoke test, with the naming convention of *.cloudfront.net/smoke-{version}.html
Verified testing in gamma

[qhanam]

lgtm pending @limhjgrace question

[adebayor123]

New Tests:

• local environment & no URL => Uses localhost
• local environment & custom URL with path => Uses custom URL
• local environment & custom URL without path => Uses .{com|net}/smoke-{version}.html
• Verified in gamma stage: https://github.com/adebayor123/aws-rum-web/runs/6481046195?check_suite_focus=true

Verified:

• Generates test URL based on the package version
• Smoke test applications names include the version