[Bug]: openjdk17-openjdk25 checkver no longer works on superseded jdk.java.net pages

[B67687]

Prerequisites

• I have searched all issues/PRs to ensure it has not already been reported or fixed.

What happened?

The checkver logic for the openjdk17 through openjdk25 manifests in the Java bucket no longer works.

These manifests currently scrape https://jdk.java.net/<major> pages, but those pages now return superseded-release pages in PowerShell/checkver instead of the old download layout the regex expects. As a result, checkver.ps1 fails for every manifest in this family.

Package name

openjdk17-openjdk25

Expected behavior

checkver should continue to detect the current archived GA Windows x64 builds for the openjdk17 through openjdk25 manifests.

Additional context/output

Current failures include:

openjdk17: couldn't match ... in https://jdk.java.net/17
openjdk21: couldn't match ... in https://jdk.java.net/21
openjdk24: couldn't match ... in https://jdk.java.net/24
openjdk25: couldn't match ... in https://jdk.java.net/25

I verified locally that the same issue affects openjdk17, openjdk18, openjdk19, openjdk20, openjdk21, openjdk22, openjdk23, openjdk24, and openjdk25.

A likely fix is to switch these manifests to https://jdk.java.net/archive/ and match the appropriate major-version Windows asset there instead of scraping the superseded major-version landing pages directly.

[B67687]

I have a local fix approach prepared for this checkver issue family, and I'm working on it.

[B67687]

Quick scope note from testing: the clean fix I prepared covers openjdk, openjdk17, and openjdk20 through openjdk25.

openjdk18 and openjdk19 are still affected too, but I left them out of the same patch because https://jdk.java.net/archive/ no longer exposes the exact versions those manifests currently point to (18.0.2.1-1 and 19.0.2-7). Those two look like separate follow-up work rather than a safe drop-in archive switch.