Preserve rich version declaration level when using publishing resolved version

[chali]

When I'm using the feature to publish resolved versions for my dependencies and my dependencies get resolved version via prefer constraints. I would like to see in published Gradle metadata the same rich version constraint. Currently, it will be published as require.

For example I have those dependencies:

runtimeClasspath - Runtime classpath of source set 'main'.
+--- org.apache.commons:commons-math3 -> 3.6.1
\--- org.apache.commons:commons-math3:{prefer 3.6.1} -> 3.6.1 (c)

But they are published as:

       "dependencies": [
        {
          "group": "org.apache.commons",
          "module": "commons-math3",
          "version": {
            "requires": "3.6.1"
          }
        }
      ],
      "dependencyConstraints": [
        {
          "group": "org.apache.commons",
          "module": "commons-math3",
          "version": {
            "requires": "3.6.1"
          }
        }
      ],

In more complex scenarios there could be "conflict resolution" and the strictest rich version level would win. Together with the selected version.

[jjohannes]

Related in the which version information do we publish? topic are: #10812