[eas-cli] Allow new updates to end active rollouts

[gwdp]

Note

Leaving on draft until server changes land

Why

Right now you can't publish anything for a runtime version while a rollout is in progress. A customer hit this mid-hotfix and couldn't roll back to embedded. The only ways out were pushing the rollout to 100%, or reverting, which deletes the update group

How

• Before publishing on eas update, eas update:republish, eas update:roll-back-to-embedded and eas update:rollback, we check the latest update for each platform and runtime.
• If one is mid-rollout, we warn and ask if that is the real intent.
• Upon confirmation, pass the update id from the active rollout, so the server ends it once the new update can actually be served. The flag --force-end-active-rollout skips the prompt, and non-interactive needs it

Worth highlighting -> if your new update is itself a rollout, the old one becomes your control update, so its share grows. A 2% rollout over a 20% one leaves the old one serving 98%

Test Plan

• Local run with local www/website
• CI w/ full coverage on newer code

[linear-code]

ENG-25976

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.82%. Comparing base (ce93a92) to head (09cd9e0).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4233      +/-   ##
==========================================
+ Coverage   63.73%   63.82%   +0.09%     
==========================================
  Files        1030     1031       +1     
  Lines       47448    47548     +100     
  Branches     9977    10011      +34     
==========================================
+ Hits        30237    30341     +104     
+ Misses      17110    17106       -4     
  Partials      101      101              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

✅ Thank you for adding the changelog entry!