buildpipeline generator set trigger even if triggerSchedule_nightly not in the config file

[andrew-m-leonard]

jdk-21 pipeline job trigger was randomly getting set to a triggerSchedule_nightly, even though the jdk21.groovy config has no value....?

It seems in Jenkins groovy, a local "def target" variable that is not initialized within an iterative loop, will still have the values from the previous iteration! Hence, the jdk21 iteration was picking up the jdk17u or jdk20u schedule!!