Expand comparison scmReference and JDK_BRANCH value from testenv.properties to cover Adoptium patch use case

[smlambert]

The current code in openjdk_build.groovy that checks if we are using appropriately matched test material to the JDK code that we are building does not take into account the very occasional use case where we will float a patch in the Adoptium mirror repo ahead of it being upstreamed to the OpenJDK repository. Since we are about to do just that for the April 2024 CPU release for s390x_linux patch into JDK 22, we need to update the comparison code.

Related code:
https://github.com/adoptium/ci-jenkins-pipelines/blob/master/pipelines/build/openjdk_pipeline.groovy#L80-L83
https://github.com/adoptium/ci-jenkins-pipelines/blob/master/pipelines/build/openjdk_pipeline.groovy#L106-L114