Audit all plugins on our jenkins server

Follow-on to the work done in https://github.com/adoptium/infrastructure/issues/2108:
We have been using the current jenkins server for some time and we should look at all the plugins that we have in order to ensure the following:
- Anything we rely on is being kept patched from a security perspective (i.e. has some sort of maintainer)
- Everything we have installed is understood and we have a record of what it is needed and used for
- Ensure that we can recreate the server from scratch if required with the plugins we need.
As a starting point for some that are required, the ones used in our private jenkins server are listed at https://github.com/eclipse-cbi/jiro/blob/master/instances/adoptium.temurin-compliance/target/jenkins/plugins-list.txt and should be a subset of the ones we have on the public server.

Start by reviewing the follow-on issue 2108 and the private-server reference at jiro/instances/adoptium.temurin-compliance/target/jenkins/plugins-list.txt. Audit the public Jenkins server's installed plugins, recording each plugin's purpose, usage, and security maintenance status. Done means the required set is documented and the server can be recreated with those plugins.

Written by the indexing model from the issue text.