Consuming preferred dependencies is unexpected across Gradle, Maven, and Ivy metadata

[OdysseusLives]

Tracking gradle/gradle#7351

I'm raising this as an issue/ conversation topic as it relates to functionality not part of Ivy or Maven metadata, but an interesting user flow of:

1. User defines preferred dependency version in a project
2. User publishes with Maven or Ivy or Gradle metadata format
3. User consumes dependency in another project
4. User expects to resolve to the preferred transitive dependency version

That will have a different outcome depending on what metadata format is used.

Mainly, I'd like a discussion/ clarification/ README section that details what I should expect with these use cases.