SOLR-17602: Per-Module Dependency Locking

[malliaridis]

https://issues.apache.org/jira/browse/SOLR-17602

Description

To improve the developer experience of the dependency management, we are looking for solutions to make the dependency lock files more developer-friendly / readable.

Solution

This solution is based on #2915 which introduces a platform module for aligning the dependency version across our project via constraints.

This PR removes the carrotsearch dependencycheck plugin and falls back to the default gradle tasks for generating lockfiles. It defines a new task that can be used via gradlew resoslveAndLockAll --write-locks. This task generates or updates existing gradle.lockfile in each module.

Additional gradle configuration has been added to lock all module configurations by default. The task resolveAndLockAll will then filter and lock only the resolveable dependencies.

PR should update documentation before merging (in case this solution is considered).

Tests

No tests have been made yet.

Checklist

Please review the following and check all that apply:

• I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
• I have created a Jira issue and added the issue ID to my pull request title.
• I have given Solr maintainers access to contribute to my PR branch. (optional but recommended, not available for branches on forks living under an organisation)
• I have developed this patch against the main branch.
• I have run ./gradlew check.
• I have added tests for my changes.
• I have added documentation for the Reference Guide