[Gradle manager] Bug in updating common dependency

[LarsSven]

Tell us more.

We have a gradle project that essentially works as follows:
We define a version that Renovate detects in gradle.properties. This version is then actually used by 2 dependencies throughout the project. These 2 dependencies will eventually have the same version, but one may update a day before the other one does. When one updates, Renovate creates an MR to update the version in gradle.properties, which then breaks the project because the other dependency can't be updated yet.

Renovate should preferably check that all dependencies using the version have the version available before suggesting the upgrade.