Wrong usage of Milestone Release Qualifier for jakarta.inject-api artifact

Nobody has claimed this yet.

There was a (at least assumed from the name) milestone release [here](https://mvnrepository.com/artifact/jakarta.inject/jakarta.inject-api/2.0.1.MR) with version `2.0.1.MR` and even though central reports a [new version](https://mvnrepository.com/artifact/jakarta.inject/jakarta.inject-api/2.0.1) as `2.0.1` this is actually wrong.

According to the [Version Order Specification](https://maven.apache.org/pom.html#version-order-specification) MR is treated as a plain qualifier and therefore **higher** than `2.0.1`, to be correctly recognized as a milestone release it is only allowed to have a singe character immediately followed by a number like M1, M2, ... as it is correctly done for RC releases already.


Sadly this can't be fixed by now but should be avoided in new releases as it might confuse automatic tools that try to suggest new versions. Even though it looks like released on the same day one can see that there are already 93 references to this "false" artifact.

Start by reviewing the Maven Version Order Specification and the jakarta.inject-api release process, since the issue names no repository files or tests. Verify how milestone and release qualifiers are currently selected; done means future releases avoid the MR qualifier pattern and any relevant release guidance reflects the correct naming rule.

Written by the indexing model from the issue text.