Centralize dependency versions using constants across multiple build.gradle files

Is your feature request related to a problem?
Currently, our project consists of several subprojects, each with its own build.gradle file. Many of these subprojects share common dependencies, and it's crucial that the versions of these shared dependencies remain consistent across all subprojects.

Current situation:

• Dependency versions are specified as string literals directly in each build.gradle file.
• When a shared dependency needs to be updated, we have to manually change the version in multiple build.gradle files. Examples:
  • #3083
  • #2307
  • #1829
  • #1586
• This approach is error-prone and time-consuming, especially as our project grows.

What solution would you like?
Create a single source of truth for dependency versions in the root build.gradle, defining constants for each shared dependency version. Reference these constants in all subproject build.gradle files instead of using string literals.

Start with the root build.gradle and compare dependency version string literals across the subproject build.gradle files. Inventory shared dependencies and determine which versions should be centralized; done means those subprojects reference the root constants consistently instead of duplicating shared versions.