windows installer pipelines fail if using a non-latest tag in build pipelines

[sxa]

If you run a Windows build pipeline with a an SCM_REF value that isn't the latest one (e.g. jdk-21.0.6+5_adopt instead of jdk-21.0.6+6_adopt at the time of writing) then the installer job fails.

Also since the log is a bit "noisy" it's quite difficult to see the underlying failure.

Example: https://ci.adoptium.net/job/build-scripts/job/release/job/create_installer_windows/1194/console which pulled this zip file which has a top level jdk-21.0.6+6/ but identifies itself as 21.0.6+5. The build pipelines are overriding the version number when creating the top level directory: https://github.com/adoptium/temurin-build/blob/8646220187f9e64087249085e519a9d3d18ae97e/sbin/build.sh#L314C36-L314C65

In the installer pipelines PRODUCT_SHORT_VERSION gets set to 21.0.6+5 (and PRODUCT_FULL_VERSION=21.0.6.0.5 so the log has this, which is the underlying failure:

looking for .\SourceDir\OpenJDK-Latest\hotspot\x64\jdk-21.0.6+5
SOURCE Dir not found / failed
Listing directory :
F:\workspace\workspace\build-scripts\release\create_installer_windows\wix\SourceDir\OpenJDK21
F:\workspace\workspace\build-scripts\release\create_installer_windows\wix\SourceDir\OpenJDK21\hotspot
F:\workspace\workspace\build-scripts\release\create_installer_windows\wix\SourceDir\OpenJDK21\hotspot\x64
F:\workspace\workspace\build-scripts\release\create_installer_windows\wix\SourceDir\OpenJDK21\hotspot\x64\jdk-21.0.6+6
F:\workspace\workspace\build-scripts\release\create_installer_windows\wix\SourceDir\OpenJDK21\hotspot\x64\jdk-21.0.6+6\bin
F:\workspace\workspace\build-scripts\release\create_installer_windows\wix\SourceDir\OpenJDK21\hotspot\x64\jdk-21.0.6+6\conf
F:\workspace\workspace\build-scripts\release\create_installer_windows\wix\SourceDir\OpenJDK21\hotspot\x64\jdk-21.0.6+6\include