Ref #4894: Make Groovy DSL ITs platform compliant

[essobedo]

fixes #4894

Motivation

The Groovy DSL tests are hard to make work on the Quarkus Platform.

Modifications

• Revert changes that were required to workaround the ClassLoading issue

[essobedo]

@ppalaga I've just checked and refreshed my mind a bit about it, the problem here is very specific and complex, it only occurs when using the Quarkus JUnit5 extension with Groovy extensions. The Groovy extensions are loaded with the System ClassLoader instead of the Quarkus Runtime ClassLoader because Groovy is declared as a parent first artifact in Quarkus core that is why the Camel extensions are not seen. Groovy has been declared as a parent's first artifact to fix a ClassValue leak in Quarkus described in this ticket. In theory, the way to fix the leak is more or less what is done in the GroovyCacheCleaner in case Groovy is in the System CL but if Groovy is in a custom CL like Quarkus Runtime ClassLoader it gets even more complex to clean up the ClassValue so I'm testing another approach that simply disables the ClassValue in Groovy if the tests pass I will propose the ticket and the corresponding PR hoping that they will accept them otherwise I'm afraid that the only way is to keep the code as it is in camel-quarkus and apply your proposal in Quarkus Plarform. I don't think it is worth too much effort since once again it is a very specific use case and having Groovy classes loaded in the Quarkus Runtime ClassLoader may have an impact on the duration of the tests since it will load potentially several times the Groovy classes per module instead of only once.

[essobedo]

The related ticket in Quarkus quarkusio/quarkus#34446

[ppalaga]

Thanks for investigating @essobedo!