feat(test): test IAM setup with CF templates on fresh account

[InesNi]

Description

Two main changes:

1. Merging the two CF templates used for GitHub OIDC IAM setup into one template.

This way the IAM role created will have permission needed to run tests on both Lambda and Fargate, and only one Launch Stack button will be needed in our GitHub Actions guide.

2. Adding automated tests for CloudFormation (CF) templates

Testing that the IAM role created from the github-oidc.yml CF template has the correct permissions to be able to run Artillery tests on Lambda and Fargate and that the OIDC is set correctly.

• We do this by building on the Publish CloudFormation templates to AWS S3 Github action creating the following flow:

  • The templates are published to S3
  • Then the set-up-and-run-artillery-test-on-aws job runs for both Lambda and Fargate but one at a time:
    • Relevant resources are deleted from the AWS account used for testing with aws-nuke, essentially simulating a fresh account
    • We get the GitHub OIDC template from S3 and deploy the stack
    • The created ArtilleryGitHubOIDCRole IAM role is assumed
    • Existing test files are triggered: the lambda-smoke.test.js for Lambda and dd-adot.test.js for Fargate.

• The action will be triggered by Publish packages to NPM and Publish packages to NPM (canary) runs. Due to this a canary version of templates has been implemented as well.

Pre-merge checklist

• Does this require an update to the docs?
• Does this require a changelog entry?