Spock's versioning confuses Dependabot

Describe the bug

Due to the versioning scheme of Spock 2.x having the Groovy compatibility encoded in the version, Dependabot will always send updates to the groovy-4 variant.

To Reproduce

1. Create a Gradle project with a dependency to org.spockframework:spock-core:2.1-groovy-3.0
2. Enable Dependabot and chose gradle as the package-ecosystem
3. Wait
4. You will get a PR that tries to update to org.spockframework:spock-core:2.3-groovy-4.0 (or whatever the latest 2.x release is at that time)

Expected behavior

Spockframework should use the classifier portion of the GAV to indicate Groovy compatibility. That way Dependabot can distinguish between the two Groovy variants.

Actual behavior

Spockframework appends the variant information to the version number, which isn't recognized by Dependabot.

Java version

N/A

Buildtool version

N/A

What operating system are you using

Mac

Dependencies

org.spockframework:spock-core:2.1-groovy-3.0

Additional context

No response

Start by reviewing how Spock 2.x publishes its spock-core dependency coordinates and how the Groovy variants are represented. Determine the release and dependency metadata that Dependabot reads, then verify that a Groovy 3 dependency remains on the Groovy 3 variant rather than being upgraded to Groovy 4.