DevMode Runtime ClassLoader is never closed

[Sanne]

Describe the bug

Tracing the constructors and close methods on QuarkusClassLoader one can see that during a live-reload this is the sequence of relevant events:

• start a new "Deployment Class Loader: DEV"
• stop a "Deployment Class Loader: DEV"
• start a new "Quarkus Runtime ClassLoader: DEV"

So at each re-deply, two new classloaders are constructed, but only one is being closed. The "Runtime ClassLoader" is never explicitly closed.

It doesn't seem critical: as far as I can tell with limited testing this doesn't seem to result in a real leak, and the classloader is still eventually collected by GC.

The closeTasks runnables that could be registered on a "Quarkus Runtime ClassLoader: DEV" are also not executed, but as far as I can see these are typically an empty list.

ResourceBundle.clearCache is also not being processed, but this also seems harmless in pracice.

@stuartwdouglas could you have a look? Feel free to close if it's intended.

Quarkus version or git rev

main @ dcf7c09377