[JENKINS-37032] Add a UI to allow controlling enabled agent protocols

- Also switch the A/B testing of JNLP3-connect to via opt-in
- Also mark that JNLP3-connect will be deprecated by JENKINS-36871
- Also start A/B testing the disabling of JNLP-connect and CLI-connect (should be well safe by now)

[FIXED JENKINS-37041] Ensure that detached plugins are always at least their minimum version

[JENKINS-29922] Correct the default value handling of ArtifactArchiver.excludes

Tests are not run unless the class name ends with "Test"

[FIXED JENKINS-36996] Hide the Java Web Start launcher when the TCP agent port is disabled

* [JENKINS-36908] Make sure that the All view is created

* Revert old All view behaviour

* Fix changed comment

* Tests

* Delete unwanted file.

[JENKINS-36871] Allow accessing instance identity from core

[JENKINS-36923] Give ownership of bcpkix dependency to bouncycastle-apl plugin

- We are committed to this now that bouncycastle-api 2.16.0 has been released

* [FIXED JENKINS-34882] Honor non-default update sites during install

* Fix pluginSetupWizard tests

* Fix lint

- We now check the format and assure that all detached plugins are reported

Adding a few nullability annotations

- We will be asking users who wish to ensure a secure path for their JNLP agents to validate the fingerprint before initial connection (which leverages TLS encryption of the http end-point and trust by the JNLP agent of the Jenkins Master's HTTPS TLS certificate)
- The fingerprint will then be used to validate the JNLP self-signed TLS certificate in order to ensure that the agent is talking to the master without fear of MiM
- We need to use self-signed TLS certificates for the JNLP connection as we need these to be unique to the Jenkins master and if we let users provide their own then they would end up re-using... in any case it is simpler to leverage the strength of the HTTPS TLS certificate as that is at least the one certificate that users have a hope of understanding how to validate.
- Thus we need a mechanism for users to verify the fingerprint. This root action provides that mechanism