Add new testJobType for release

[smlambert]

Fixes #847
Add an explicit testJobType for release pipeline, which allows us to add non-blocking testing to weekly runs

[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"

[karianna]

@smlambert

RepoHandlerTest > adoptDefaultsGetterReturns() FAILED
org.opentest4j.AssertionFailedError: expected: but was:
at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:40)
at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:35)
at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:162)
at org.junit.jupiter.api.Assertions$assertTrue$1.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:139)
at RepoHandlerTest.adoptDefaultsGetterReturns(RepoHandlerTest.groovy:70)

[smlambert]

@karianna - Looking at https://github.com/adoptium/ci-jenkins-pipelines/blob/master/docs/UsingOurScripts.md#this-is-great-but-how-do-i-add-new-defaults , it is expected that a newly added test will fail.

You may find that the RepoHandlerTest.groovy:adoptDefaultsGetterReturns() will fail when you add new values. This is expected as the test is pulling in Adopt's master branch defaults.json which does not yet contain the new values. Please inform any reviewers of this in the pull request.

[andrew-m-leonard]

looks good I think

[sophia-guo]

LGTM

[smlambert]

I will proceed to merge, and monitor the next PR test runs on a different PR, to ensure these new tests are "good".