fix(release): wait longer for npm to serve a newly published version

[roncodes]

Problem

The v2.1.0 release published to npm successfully, but its next step, "Verify registry checksum and clean consumers", failed.

• The step asks npm for the new version's metadata.
• npm kept returning 404, because a just-published version can take a few minutes to become available.
• The script gave up after 6 attempts, 10 seconds apart (about 1 minute).
• Because that step failed, the GitHub release and the GitHub Packages mirror were skipped.

Re-running the failed job recovers it. The publish step finds identical bytes already on npm and does not publish again, the existing tag already points at the same commit, and by then verification passes.

Change

scripts/verify-published.mjs now retries for about 11 minutes, backing off from 10 to 60 seconds between attempts. That fits inside the release job's 25-minute timeout. Nothing else changes.

This is a tooling-only change on main, not a release. It doesn't publish anything.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (696c10c) to head (7b1b009).

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #50   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           18        18           
  Lines          860       860           
  Branches       143       143           
=========================================
  Hits           860       860           

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