Feature: use a node pool (labeles) for job "Cleanup-Nodes"

https://ci.adoptopenjdk.net/job/Cleanup-Nodes/ is set to use [test-packet-ubuntu2004-x64-2](https://ci.adoptopenjdk.net/computer/test-packet-ubuntu2004-x64-2/)’

current this node is offline , look back from history it has been offline at least back from 3rd Nov. https://ci.adoptopenjdk.net/job/Cleanup-Nodes/56/console
So, we have no cleanup for at least 2 weeks on these nodes.

```
Agent test-packet-ubuntu2004-x64-2 (4 CPUS | 8 GB RAM | 80 Gb SSD | hosted by packet.net)
This agent is offline because Jenkins failed to launch the agent process on it. [See log for more details](https://ci.adoptopenjdk.net/computer/test-packet-ubuntu2004-x64-2/log)
```

P.S:
source code of this job is from https://github.com/eclipse-openj9/openj9/blob/master/buildenv/jenkins/jobs/infrastructure/Cleanup-Nodes.groovy
Do we have a forked version in our repo? or is it safe to keep using "master" branch?

Start with the Cleanup-Nodes Jenkins job and its history, then read buildenv/jenkins/jobs/infrastructure/Cleanup-Nodes.groovy in the referenced OpenJ9 repository. Confirm whether this repository has a forked version or safely uses master. Done means the job uses a node pool selected by labels and cleanup is no longer tied to the offline node.

Written by the indexing model from the issue text.