Fix change verification after peer dependency version bumps

[Bharat Middha (bmiddha)]

Summary

Fixes the remaining rush change --verify false positives after rush version --bump seen in the automated rush and noRush bump PRs (#6009 and #6010).

When excludeVersionOnlyChanges is enabled, ProjectChangeAnalyzer now ignores a changed project-root package.json only when:

• the package's own top-level version changed;
• its package name is unchanged; and
• every other field except peerDependencies is unchanged.

This intentionally permits arbitrary peer dependency additions, removals, or range rewrites alongside the package's own version bump. Changes to dependencies, devDependencies, optionalDependencies, or any unrelated package field remain substantive and still require a change file. Existing root CHANGELOG.md / CHANGELOG.json handling is unchanged.

Validation

• node ../../common/scripts/install-run-rushx.js test --test-path-pattern ProjectChangeAnalyzer from libraries/rush-lib: 34 passed.
• node common/scripts/install-run-rush.js build --to @microsoft/rush-lib: passed, including TypeScript, ESLint, and API Extractor.
• Built the modified local Rush and copied only its lib-commonjs and dist output into clean detached origin/main snapshots, then invoked the engine directly rather than allowing install-run-rush to select published Rush 5.178.1:
  • node libraries/rush-lib/lib-commonjs/start.js version --bump --version-policy rush
    • changed 85 package manifests;
    • node libraries/rush-lib/lib-commonjs/start.js change --verify passed.
  • node libraries/rush-lib/lib-commonjs/start.js version --bump --version-policy noRush
    • changed 74 package manifests;
    • node libraries/rush-lib/lib-commonjs/start.js change --verify passed.
  • After the noRush bump, manually changed and staged @rushstack/heft-lint-plugin's non-peer dependencies.semver range from ~7.7.4 to ~7.7.3.
    • direct local change --verify failed with exit code 1 and reported @rushstack/heft-lint-plugin, as expected.

The automated pipelines currently select published Rush 5.178.1 through install-run-rush. Existing bump PRs will not gain this behavior until a Rush release containing this fix is published and selected (or an equivalent preview/local selection is used) before regenerating the bumps.