fix(publish): update @next dist-tag on stable npm releases

[jdutton]

Summary

• publish-with-rollback.ts adds a Phase 2 that calls npm dist-tag add <pkg>@<version> next on all packages when UPDATE_NEXT=true, with rollback on failure
• Previously @next was only set during RC publishes; after a stable release it stayed pinned to the last RC indefinitely
• Set UPDATE_NEXT=true from your publish workflow via determine-publish-tags.ts to activate Phase 2 on stable releases

Test plan

• CI passes on this PR
• After merge, wire determine-publish-tags.ts into your publish.yml and verify @next updates on the next stable release

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.54%. Comparing base (e1e1b3d) to head (c76e7f6).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main       #4   +/-   ##
=======================================
  Coverage   85.54%   85.54%           
=======================================
  Files           2        2           
  Lines          83       83           
  Branches       27       17   -10     
=======================================
  Hits           71       71           
  Misses         12       12           

🚀 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.