Added in support for Microsoft's Build of OpenJDK

[thozook]

Resolves issue reported in #3719

Used the previous "$jvmHotSpot" variable since the registry key for Microsoft's OpenJDK build is also in the same hotspot subdirectory.

[anatolybolshakov]

@thozook thanks! Let us take a look

[AndreyIvanov42]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[hymccord]

@anatolybolshakov Any movement on this PR?
I build self-hosted agent images using https://github.com/actions/runner-images
These images use the Microsoft OpenJDK and the agent does not add JAVA as a system capability. I have to add it manually.

I would edit the powershell files myself, but those changes would be wiped out on agent upgrade correct?

[anatolybolshakov]

Hi @hymccord I'm no longer working on project - @kirill-ivlev would probably be the right person to address

[LarsLaskowski]

#3719 is closed, but the issue is still available. I think it makes sense that the Microsoft OpenJDK installation is also recognized by the agent. I just had to go back to Adoptium Eclipse today because it doesn't work. What a pity.

[MichelZ]

@aleksandrlevochkin @kirill-ivlev I was having an issue with a self-hosted agent and Microsoft Java recently. This would have prevented the issue I think. Can this be merged?

[bdovaz]

Any updates? Thanks.

Related #3624