Disable e2e-autoscaling test when pushing images to staging

[tbavelier]

What does this PR do?

• Removes the e2e-autoscaling step for manual pipelines

Motivation

• Avoid being blocked by this long test when pushing images to staging (n.b.: the e2e regular tests have allow_failure: true so they can be cancelled manually if needed unlike this one, where cancelling it prevents from going to next step)

Additional Notes

Anything else we should know when reviewing?

Minimum Agent Versions

Are there minimum versions of the Datadog Agent and/or Cluster Agent required?

• Agent: vX.Y.Z
• Cluster Agent: vX.Y.Z

Describe your test plan

Verified in https://gitlab.ddbuild.io/DataDog/datadog-operator/-/pipelines/99702629 that e2e-autoscaling is no longer present when PUSH_IMAGES_TO_STAGING is set

Checklist

• PR has at least one valid label: bug, enhancement, refactoring, documentation, tooling, and/or dependencies
• PR has a milestone or the qa/skip-qa label
• All commits are signed (see: signing commits)

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 38.69%. Comparing base (f978413) to head (1574d57).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2672   +/-   ##
=======================================
  Coverage   38.69%   38.69%           
=======================================
  Files         307      307           
  Lines       26526    26526           
=======================================
  Hits        10265    10265           
  Misses      15495    15495           
  Partials      766      766           

Flag	Coverage Δ
unittests	38.69% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f978413...1574d57. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[tbavelier]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-03-02 10:02:50 UTC ℹ️ Start processing command /merge

---

2026-03-02 10:02:57 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2026-03-02 10:20:16 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 2h (p90).

---

2026-03-02 12:15:19 UTC ℹ️ MergeQueue: This merge request was merged