tf: configurable ec_target for smoke and benchmark

[carsonip]

Motivation/summary

Consolidate Elastic Cloud target handling for benchmark and smoke test Terraform/workflow paths, while keeping integration server test target passthrough semantics unchanged.

This update:

• standardizes benchmark target support around ec_target values qa|pro
• moves admin console URL mapping into the shared ec_deployment Terraform module and passes ec_target through from benchmark
• updates smoke tests to use EC_TARGET with target-to-API-base mapping in testing/smoke/lib.sh
• aligns workflow defaults for QA-keyed jobs (benchmarks and smoke-tests-os) with qa

Checklist

• Update CHANGELOG.asciidoc
• Documentation has been updated

For functional changes, consider:

• Is it observable through the addition of either logging or metrics?
• Is its use being published in telemetry to enable product improvement?
• Have system tests been added to avoid regression?

How to test these changes

• terraform fmt -recursive
• Validate smoke API base selection from EC_TARGET in testing/smoke/lib.sh:
  • qa -> https://public-api.qa.cld.elstc.co
  • pro -> https://api.elastic-cloud.com
  • endpoint calls append /api/v1/...
• Validate benchmark target wiring:
  • testing/benchmark/main.tf passes ec_target to module "ec_deployment"
  • provider ec endpoint map still uses API hosts (api_endpoints)
• Validate admin console URLs:
  • testing/infra/terraform/modules/ec_deployment/outputs.tf maps:
    • qa -> https://admin.qa.cld.elstc.co
    • pro -> https://admin.found.no

Related issues

Fixes #21268
Supersedes #21269
Follow up to #21222

[prodsecmachine]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify]

This pull request does not have a backport label. Could you fix it @carsonip? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8.19 is the label to automatically backport to the 8.19 branch.
• backport-9./d is the label to automatically backport to the 9./d branch. /d is the digit.
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[carsonip]

Blocked by #21275

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: a909c44

History

• 💚 Build #11204 succeeded fe00fa8