Allow loading custom Groovy extension modules

[essobedo]

fixes #34446

Motivation

The custom Groovy extension modules cannot be detected from the System classloader

Modifications:

• No more defines Groovy as a parent first artifact
• Adds GroovyClassValue to disable the usage of ClassValue in Groovy
• Removes GroovyCacheCleaner as it is no more used

[geoand]

Interesting approach. Are you sure this avoids memory leaks? How did you test?

[essobedo]

Interesting approach. Are you sure this avoid memory leaks?

Yes I'm sure I have tested it against my small project and the test project defined in #12498 with 30 tests instead 10 initially

[essobedo]

Actually, the problem is related to the ClassValue added to the JDK for languages like Groovy but they are very hard to clean up, the only way I know is the one described in this SO answer but in some use cases it can be too much and can have side effects

[essobedo]

It looks like the CI is unstable because Maven Tests - JDK 11 Windows fails in my repo while JVM Tests - JDK 17 Windows passes as you can see here, and here it is the exact opposite. Moreover, I would be surprised if those changes were really OS-specific.

[essobedo]

Another remark is about the duration of some Jobs that seem to be very long, I don't know if it is common or not?

[essobedo]

I see more or less the same results (duration + failing tests) in another PR #34417

[geoand]

Yeah, those seem to be flaky tests

[quarkus-bot]

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.