Release Candidate 4 for the aggregated dependency-resolution engine

Fixes a maven_install repository being dropped from the generated WORKSPACE when
every artifact in it was override-mapped, while targets still emitted labels into
it — which failed Bazel analysis with no such package. Adds generation-time
validation that fails the build when an emitted label names a repository that is
not rendered, or an artifact absent from the repository its label names, plus a
sample fixture reproducing the shape.

Note for consumers: repositories that were previously dropped now render, so new
*_maven_install.json lockfiles may appear and need committing.

Release Candidate 3 for the aggregated dependency-resolution engine

Resolves the dependency graph top-down from binary roots instead of per-module,
with per-variant bucketing by set-intersection and a local Maven proxy backing
the pin. This RC additionally moves the databinding metadata task onto the same
binary roots (1m44s -> 0.5s on PAX, byte-identical output) and makes the proxy's
resolution summary user-facing.

Release Candidate 2 for changes in grazel-gradle-plugin to suit Bazel…

… 8 migration

Release Candidate 1 for changes in grazel-gradle-plugin to suit Bazel…

… 8 migration

Use resources attribute for JVM classpath resources in kt_jvm_library

Use resources attribute for JVM classpath resources in kt_jvm_library

Make resolved graph gc able

Release version 0.4.2-alpha.17

Fix KSP maven artifacts never being pinned or resolved (#173)

Release version 0.4.2-alpha.15