Refactor global build info plugin to leverage JavaInstallationRegistry (#54026)

This commit removes the configuration time vs execution time distinction
with regards to certain BuildParms properties. Because of the cost of
determining Java versions for configuration JDK locations we deferred
this until execution time. This had two main downsides. First, we had
to implement all this build logic in tasks, which required a bunch of
additional plumbing and complexity. Second, because some information
wasn't known during configuration time, we had to nest any build logic
that depended on this in awkward callbacks.

We now defer to the JavaInstallationRegistry recently added in Gradle.
This utility uses a much more efficient method for probing Java
installations vs our jrunscript implementation. This, combined with some
optimizations to avoid probing the current JVM as well as deferring
some evaluation via Providers when probing installations for BWC builds
we can maintain effectively the same configuration time performance
while removing a bunch of complexity and runtime cost (snapshotting
inputs for the GenerateGlobalBuildInfoTask was very expensive). The end
result should be a much more responsive build execution in almost all
scenarios.

(cherry picked from commit ecdbd37f2e)

plugins/discovery-ec2/build.gradle

@@ -117,11 +117,9 @@ thirdPartyAudit.ignoreMissingClasses(
   'org.apache.log.Logger'
 )
 
-rootProject.globalInfo.ready {
-  if (BuildParams.runtimeJavaVersion > JavaVersion.VERSION_1_8) {
-    thirdPartyAudit.ignoreMissingClasses(
-      'javax.xml.bind.DatatypeConverter',
-      'javax.xml.bind.JAXBContext'
-    )
-  }
+if (BuildParams.runtimeJavaVersion > JavaVersion.VERSION_1_8) {
+  thirdPartyAudit.ignoreMissingClasses(
+    'javax.xml.bind.DatatypeConverter',
+    'javax.xml.bind.JAXBContext'
+  )
 }