Avoiding dependency hell with Gradle 6

Gradle 6 introduces a richer dependency management model to tackle common dependency hell problems such as version conflicts, misaligned module versions, vulnerable transitive dependencies, and dynamic version instability. Key features include rich version constraints (strictly, prefer, reject ranges), Gradle Module Metadata published by default, platforms for centralized version declarations, dependency version alignment, capabilities to resolve conflicting implementations, optional feature variants, and dependency locking for reproducible builds. These tools are now available to both library authors and consumers via published modules, not just in multi-project setups.