Make 'Nightly Without Publish' the default choice for openjdkNN-pipeline jobs to avoid accidental publishing

[andrew-m-leonard]

Fixes: #1059

Changed the pipeline job generation default releaseType choice to "Nightly Without Publish" to avoid accidental publishing of test builds.
Note:

• triggered EA beta builds specifically set "Weekly" (with publish):

  ci-jenkins-pipelines/pipelines/build/common/trigger_beta_build.groovy

  Line 252 in e960c25

  string(name: 'releaseType', value: "Weekly"),

• scheduled Oracle managed weekly releases (eg.currently jdk22u) use the weekly-openjdkNN-pipeline job, which still defaults to "Weekly" (with publish)

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

[andrew-m-leonard]

run tests

[eclipse-temurin-bot]

 PR TESTER RESULT 

❎ Some pipelines failed or the job was aborted! ❎
See the pipeline-build-check below for more information...