fix(spawn-local-jdk): recognize and launch Windows JDK homes

[deer]

JDKDetector.of rejected any JDK home that lacked a bin/java file, which meant a staged Windows JDK -- one that ships only bin/java.exe -- was silently rejected before its release file was ever read, so the foreign-platform OperatingSystem/Architecture tagging added in #50 was unreachable for the one case it was built for.

This updates the bin/java existence check to also accept bin/java.exe, and updates LocalJDKLauncher#getExecutable to build the launch command with bin/java.exe on Windows and bin/java elsewhere, based on OperatingSystem.current(), so a detected Windows JDK can actually be launched rather than just recognized.

It also adds windows@... glob rules to java.home.properties for common Windows JDK install locations (Oracle, Zulu, Eclipse Adoptium, Microsoft Build of OpenJDK, Amazon Corretto, SDKMAN, Scoop, and GitHub Actions Windows runners). JDKHomeBasedPatternDetector#matchesOS already supported the windows OS-pattern prefix, but the properties file had zero entries using it, so paths() returned nothing on a native Windows host.