[JENKINS-21486] Fix plugin dependencies resolution, second round.

version

version

missing

messages between console and administrative monitor

* Check that dependencies are enabled. A disabled optional dependency
  will not prevent a plugin from loading.
* Check versions of dependencies declared by a plugin before loading it.
  If any dependency (even optional) is older than what is required,
  then the plugin isn't loaded.

This should prevent use cases where a plugin is loaded but one of its
dependencies is too old so that :
* its @Extension annotated classes cannot be loaded, causing the full
  Jenkins to blow up with crapload of exceptions which are tedious to
  investigate to understand the root cause.
* NoSuchMethodError and the likes at runtime even though boot has
  completed.

Version check (for setups where version list is manually crafted but yet
works) can be disabled by starting Jenkins with

-Dhudson.PluginWrapper.dependenciesVersionCheck.enabled=true

Minor fixes done while implementing this change :
* Fix version parsing in PluginWrapper.Dependency
* Dynamic plugin load didn't check for disabled flag

[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