fix(client-test-version-utils): restore resolveRangeViaManifest behavior

[jason-ha]

Cleanup from #27521 CI repair:

• restore behavior of resolveRangeViaManifest to only allow version that is within manifest
• update unit tests to check expectations
• remove getRequestedVersion from package exports
• require requested be specified when calling getRequestedVersion
• add/correct various comments

Cleanup from #11082:

• correct getRequestedVersion throwing test cases (that weren't checking error message content)
• remove extraneous try-catch and wrap in calculateRequestedRange

[Copilot]

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

[github-actions]

Hi! Thank you for opening this PR. Want me to review it?

Based on the diff (110 lines, 3 files), I've queued these reviewers:

• Correctness — logic errors, race conditions, lifecycle issues
• Security — vulnerabilities, secret exposure, injection
• API Compatibility — breaking changes, release tags, type design
• Performance — algorithmic regressions, memory leaks
• Testing — coverage gaps, hollow tests

How this works

• Adjust the reviewer set by ticking/unticking boxes above. Reviewer toggles alone don't trigger anything.

• Tick Start review below to dispatch the review fleet.

• After review finishes, tick Start review again to request another run — it auto-resets after each dispatch.

• This comment updates as new commits land; your reviewer selections are preserved.

• Start review

[CraigMacomber]

Since -0 is a thing, and is a negative number, and usually considered equal to 0, and also might make sense in this code (to try and test against the most recent release, since -1 means previous beta break), we might need to clarify or rephrase this to be unambiguous on how -0 behaves.