Fix SemVer prerelease comparison

[dipeshbabu]

Summary

• compare prerelease versions identifier by identifier according to SemVer precedence
• compare numeric identifiers numerically and below nonnumeric identifiers
• account for differing prerelease identifier counts and ASCII ordering
• add the standard SemVer precedence sequence and the previously misordered alpha.1/alpha-1 case as regression coverage

Root cause

The update notifier compared each complete prerelease string with Intl.Collator. Locale-aware comparison does not implement SemVer's identifier boundaries or precedence rules, so valid versions such as 1.0.0-alpha-1 and 1.0.0-alpha.1 could be ordered incorrectly.

Impact

Prerelease users receive update notices only when the registry version has higher SemVer precedence. Stable-version behavior is unchanged.

Overlap check

Before publishing, open issues and pull requests were reviewed and repository-wide searches were run for semver, prerelease, update notice, and version comparison. No active issue or pull request overlaps this fix. The only related search hits were already-merged work that introduced the broader update-notice and release features.

Validation

• pnpm dlx bun test --timeout 30000 ./tests-ts/update-notice.test.ts — 10 passed
• pnpm exec tsc --noEmit
• pnpm exec prettier --check src/version.ts tests-ts/update-notice.test.ts
• git diff --check