Decouple Gradle plugin releases from Graal releases

[sschuberth]

          Hi @sschuberth, thank you for the report. Unfortunately, our release engineering is deeply tied into Graal's and we're not able to release the plugin outside of the normal release schedule. The next release should happen on 18th of March.

@steve-s could you please check if the bug is really fixed?

Originally posted by @msimacek in https://github.com/oracle/graalpython/issues/462#issuecomment-2560076139

[sschuberth]

To my understanding there is no technical restriction why Grable plugin and Graal releases must be synced. As Graal releases don't come too often, and the plugin might have received a fix meanwhile, it would be great to be able to release the plugin independently of new Graal versions.

[steve-s]

As a first step, we have moved the Gradle plugin, Maven plugin, GraalPy embedding utilities, Maven archetype, and the JBang integration into a separate repository: https://github.com/oracle/graalpy-extensions.

For the next GraalVM/GraalPy release 25.0.0. we plan to release those artifacts separately (probably with some short delay after the upstream release) and then continue releasing them on their own schedule.