[v20204.04+01] Remove jdk22 pipelines as top level pipelines prefer these to 22u

[sxa]

When I added jdk22u configurations I did not remove the jdk22 ones. This appears to have the unfortunate effect of resulting in the top level *_openjdk22-pipelines kicking off jdk22 jobs instead of jdk22u there run from the wrong repository and cannot pick up the correct tags.

Ref logic in

ci-jenkins-pipelines/pipelines/build/openjdk_pipeline.groovy

Line 180 in a20199e

configPath = "${WORKSPACE}/${ADOPT_DEFAULTS_JSON['configDirectories']['build']}/${javaToBuild}_pipeline_config.groovy"

This PR removes the jdk22 files so that the logic referenced above selects the jdk22u repository

[github-actions]

Thank you for creating a pull request!

Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work).

Code Quality and Contributing Guidelines

If you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before.

Tests

Github actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our testing documentation.

In order to run the advanced pipeline tests (executing a set of mock pipelines), it requires an admin to post run tests on this PR.
If you are not an admin, please ask for one's attention in #infrastructure on Slack or ping one here.
To run full set of tests, use "run tests"; a subset of tests on specific jdk version, use "run tests quick 11,21"

[steelhead31]

lgtm