This is a fixup for 38db2a5.

Signed-off-by: Sebastian Schuberth <[email protected]>

Start a novel approach based on a stand-alone Gradle plugin (written in
Kotlin) to analyze Gradle projects. The goal is to address shortcomings of
the current implementation:

- The `init.gradle` script cannot be debugged (only `buildSrc` and
  stand-alone plugins can [1]).

- The dynamically typed Groovy code is hard to maintain.

- Analysis of modern Android apps throws exceptions due to ambiguous
  configuration / variant selection.

- Binary artifacts are unnecessarily resolved.

- Maven is used to resolve metadata about artifacts, imitating Gradle's
  resolution logic / repositories to query.

At this stage the analysis only builds up the dependency tree to limit
the complexity of this initial implementation. Parsing of package
metadata will be added in follow-up changes.

Also, the new `GradleInspector` plugin is disabled by default for now to
not interfere with the existing `Gradle` plugin.

Resolves #6158.

[1]: https://docs.gradle.org/current/userguide/troubleshooting.html#sec:troubleshooting_build_logic

Signed-off-by: Sebastian Schuberth <[email protected]>

Explicitly resolve parent POMs to ensure they are available as XML files
in the Gradle cache. Based on that, build the effective POMs for all
dependencies in order to parse package metadata from them. As the POMs are
retrieved from the Gradle cache, no download via Maven is involved.

Note that the Maven-model-specific code is mostly based on code from
`MavenSupport`, adjusted to work with slightly different classes.

Signed-off-by: Sebastian Schuberth <[email protected]>

Create remote artifacts based on the POM URLs. The hashes for the
artifacts are retrieved from the respective accompanying text files,
without downloading the artifact itself.

Note that this approach will fail for private Maven repository even if
Gradle is configured with the credentials, as this download happens
directly via OkHttp.

Signed-off-by: Sebastian Schuberth <[email protected]>

…tions

For these configurations often Gradle itself has resolution failures. As
their sole purpose is to describe the dependencies that are compiled into
an Android app, just ignore them as that is what ORT itself analyzes.

Signed-off-by: Sebastian Schuberth <[email protected]>