chore: Schedules run of acceptance and migration tests for all HashiCorp Terraform supported versions

[oarbusi]

Description

Schedule run of acceptance and migration tests for all supported versions of HashiCorp Terraform
Example Run (failed because it was manually cancelled to avoid consuming too many resources)

Link to any related issue(s): CLOUDP-219140

Type of change:

• Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
• New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR.
• Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR.
• This change requires a documentation update
• Documentation fix/enhancement

Required Checklist:

• I have signed the MongoDB CLA
• I have read the contribution guidelines
• I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
• I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
• I have added any necessary documentation (if appropriate)
• I have run make fmt and formatted my code
• If changes include deprecations or removals, I defined an isolated PR with a relevant title as it will be used in the auto-generated changelog.
• If changes include removal or addition of 3rd party GitHub actions, I updated our internal document. Reach out to the APIx Integration slack channel to get access to the internal document.

Further comments

[marcosuma]

so we're doing it weekly?

[oarbusi]

Missed this before putting it in review. Now it's fixed, will run on first Saturday of every month

[lantoli]

is this GITHUB_TOKEN needed?

[oarbusi]

yes, GitHub API has rate limiting and with the github token limits are increased, so the script does not fail

[lantoli]

LGTM, no blocker but I recommend to add output info in the script (e.g. sorted list of all X.X.0 HC releases including the ones already out of support with published and end-of-support dates) so it's easier to see any issue that could happen. (that would probably imply to get the script result in GH action using an exported variable instead of the output)