Attempt to fix IdempotentParameterMismatch

[cbeauchesne]

Motivation

Changes

Made two changes in utils/virtual_machine/aws_provider.py:

1. Unique EC2 resource identity (_start_vm): the Pulumi resource id passed to aws.ec2.Instance(...) is now f"{vm.name}-{CI_JOB_ID or uuid4}" instead of the bare vm.name, so concurrent CI jobs testing the same VM OS never share a resource identity/token space. The Name tag and everything else stays keyed off vm.name as before.
2. In-process retry (_stack_up_with_idempotency_retry): if stack.up() still fails with IdempotentParameterMismatch, it destroys the partial stack and retries up to 3 attempts in-process before falling through to the existing known-exception path (destroy + pytest.exit(3) → GitLab job retry). This should resolve most occurrences without needing a full job restart.

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• Anything but tests/ or manifests/ is modified ? I have the approval from R&P team
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added, removed or renamed?
  • Get a review from R&P team

[github-actions]

CODEOWNERS have been resolved as:

utils/virtual_machine/aws_provider.py                                   @DataDog/system-tests-core

[datadog-prod-us1-4]

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🔄 Datadog auto-retried 1 job - 1 passed on retry

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: e2ee4da | Docs | Datadog PR Page | Give us feedback!}