New Maven Bazel Support Tries to Update Stable to Unstable

[cpsauer]

Hey, wonderful Renovate folks,

I really appreciate the Bazel improvements you've been landing recently--and just got my first Maven PR from #20351

There's one snag, though: It's trying to update a stable release to an unstable one.
I think that might be a bug, since Renovate (by default) has always seemed to have the desired behavior of updating stable dependencies to newer stable versions only, but I wanted to check in first since the bug report issue template said confirmed bugs only.

For more concrete details:
Here's the log showing the update from 1.3.0 (stable) to 1.6.0-dev01 (unstable, based on the version name).

          {
            "datasource": "maven",
            "depName": "androidx.annotation:annotation",
            "currentValue": "1.3.0",
            "depType": "maven_install",
            "registryUrls": [
              "https://maven.google.com",
              "https://repo1.maven.org/maven2"
            ],
            "managerData": {
              "idx": 15
            },
            "depIndex": 15,
            "updates": [
              {
                "bucket": "latest",
                "newVersion": "1.6.0-dev01",
                "newValue": "1.6.0-dev01",
                "releaseTimestamp": "2023-02-08T18:00:00.000Z",
                "newMajor": 1,
                "newMinor": 6,
                "updateType": "minor",
                "branchName": "renovate/androidx.annotation-annotation-1.x"
              }
            ],
            "warnings": [],
            "versioning": "maven",
            "sourceUrl": "https://cs.android.com/androidx/platform/frameworks/support",
            "registryUrl": "https://maven.google.com",
            "homepage": "https://developer.android.com/jetpack/androidx/releases/annotation#1.6.0-dev01",
            "currentVersion": "1.3.0",
            "isSingleVersion": true,
            "fixedVersion": "1.3.0"
          },

Thanks so much,
Chris

[Tagging @zharinov, since he was the author of https://github.com//pull/20351, but feel free anyone to chime in if you have thoughts.]

[rarkins]

I think the answer here is the same as #15828 (comment)

i.e. -whatever suffixes don't always mean "unstable" in Maven, like they do in semver. Just because it says -DO-NOT-USE-REALLY-UNSTABLE does not make that meaningful to a machine.

Pragmatically, @zharinov has added some suffixes to our list which aren't technically considered unstable (they sort HIGHER than the unsuffixed version) but which we override to make unstable. -dev may be another one we can add.

[rarkins]

@cpsauer could you raise a new Feature Request issue for this now? The description can be short and link to this Discussion - I think it's as simple as "Use gradle versioning for maven dependencies found by bazel"? No need for a reproduction either unless you wish to

[cpsauer]

Sure thing. Gimme a sec.
Thanks for the encouragement to keep it short (and fast).

[cpsauer]

Donezo #20725

[zharinov]

We've done it, you may want to check the "retry" box in your PRs of interest to update it.

[cpsauer]

Thanks so much, again, guys. I'm sure this'll save a bunch of people configuration time using the new maven bazel support.
(Backing out my workaround presently.)