test: Enables simulation of cloud-dev using hoverfly in alert configuration acceptance tests

[AgustinBettati]

Description

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

How to run replay mode

A new environment variable is defined for both capturing and then simulating interactions with external APIs when running alert configuration acceptance tests.

1. Capture requests by doing an execution of all tests in resource_alert_configuration_test.go. The following env variable must be defined:
   REPLAY_MODE=capture
   As a result of this execution you will be able to see all captured information under ./simulations folder.
2. Simulate requests by using the following variable:
   REPLAY_MODE=simulate
   In this case the test execution will search for the specific files under ./simulations folder depending on which test is being run, and will fail if no file is available.

Implementation consideration

• The hoverfly cli was used in favor of the hoverfly Go module due to the following error encountered: HTTPS error when using Go core package to setup hoverfly instance SpectoLabs/hoverfly#1120. If additional information is provided we can followup by adjusting implementation for use the go module directly.

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

[lantoli]

I think no changes needed for this PR. if we ran this in CI in many resources there will be more chances of picking an already-used port so we might want to implement a retry mechanism in the future to try in a different port until it finds one that is free

[lantoli]

great job!

just some small comments

[lantoli]

knitpit PR title: Enables...

[lantoli]

you can do: projectID = replay.ManageProjectID(t, acc.ProjectIDExecution)

if you change ManageProjectID signature:

func ManageProjectID(t *testing.T, projectIDProvider func(testing.TB) string) string {
t.Helper()
if IsInCaptureMode() {
id := projectIDProvider(t)
...

[AgustinBettati]

thanks! adjusted

[lantoli]

LGTM, just a couple of minor comments

[oarbusi]

Nice! LGTM

[maastha]

I'd update this to say something like "for example, alert configuration..." so that we don't have to worry about updating this later when we add more.