Assess git plugin usage warning

Investigate what if anything needs to be done based on this output in the test console which we are now seeing (presumably also related to recent Jenkins plugins updates).

```
Using shallow fetch with depth 1
Fetching upstream changes from https://github.com/adoptium/aqa-tests.git
> git --version # timeout=10
> git --version # 'git version 2.35.1'
> git fetch --tags --force --progress --prune --depth=1 -- https://github.com/adoptium/aqa-tests.git +refs/heads/*:refs/remotes/origin/* # timeout=60
> git rev-parse origin/master^{commit} # timeout=10
JENKINS-19022: warning: possible memory leak due to Git plugin usage; see: https://plugins.jenkins.io/git/#remove-git-plugin-buildsbybranch-builddata-script
Checking out Revision d4a993c4cf290869d5cc0855c6623dd88c24bd15 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f d4a993c4cf290869d5cc0855c6623dd88c24bd15 # timeout=10
Commit message: "Exclude containers tests on all linux platform (#3908)"
> git rev-list --no-walk d4a993c4cf290869d5cc0855c6623dd88c24bd15 # timeout=10
```

The action may be for a Jenkins admin to follow the workaround instructions outlined at:
https://plugins.jenkins.io/git/#plugin-content-remove-git-plugin-buildsbybranch-builddata-script

Start with the Jenkins test-console output in this issue and the Git plugin workaround instructions linked in the body. Determine whether the warning requires a Jenkins administrator action and document the applicable resolution or confirm that no repository change is needed.

Written by the indexing model from the issue text.