Make Paper Gradle modules declare a capability of the old artifact ID

[zml2008]

Is your feature request related to a problem?

Because Paper changed its artifact ID starting with 1.17, normal Gradle version selection cannot tell that the old com.destroystokyo Paper is in fact the same thing as the new io.papermc.paper Paper.

This can result in both old and new artifacts ending up on the compile classpath, and potentially allowing old classes to override new classes.

Describe the solution you'd like.

Gradle provides the ability to publish 'capabilites' as part of the artifact's module metadata. This way Paper can declare that it provides a newer version of the old com.destroystokyo.paper:paper-api artifact

See https://docs.gradle.org/current/userguide/component_capabilities.html#sec:declaring-additional-capabilities-for-a-local-component

I'm not sure if Gradle will automatically select the newer version here, but at the very least it will convert silent incorrect behavior into a loud error.

Perhaps Paperweight could declare a conflict strategy of selecting the highest version, which would at least help users using userdev, example https://docs.gradle.org/current/userguide/dependency_capability_conflict.html#sub:selecting-preferred-capability-provider

Describe alternatives you've considered.

manual exclusions?

Other

No response