acceptable jakarta versions are erroneously replaced

[bjlaub]

It is possible for an acceptable version of a Jakarta lib (e.g. one with a version that already uses the jakarta namespace) to erroneously be replaced if a known "bad" version also exists on the classpath.

Consider:

dependencies {
    implementation "org:foo"
    implementation "jakarta.ws.rs:jakarta.ws.rs-api"
}

with a versions.props that reads:

org:foo = 1.0.0
jakarta.ws.rs:jakarta.ws.rs-api = 3.1.0

If org:foo:1.0.0 contains a dependency on jakarta.ws.rs:jakarta.ws.rs-api:2.1.6, we incorrectly also substitute jakarta.ws.rs:jakarta.ws.rs-api:3.1.0 with javax.ws.rs:javax.ws.rs-api:2.1.1, which is likely to cause a compile failure if e.g. this project uses classes from the jakarta namespace (which is completely valid.