refactor: Separated JDK management code into its own module

[quintesse]

Fixes #1857

[maxandersen]

we seem to call this in many places - but how is going to take into affect jbang provided config of i.e. providers?

[quintesse]

Right now the idea is that the config gets used exactly in that file you're referencing. So the builder will use the config to initialize the jdk manager, including the providers. The jdk manager itself is then completely agnostic where its configuration comes from.

[maxandersen]

ok so in jbang cli we would not call jdkmanger() but have our own instance configured from jbang config?

[quintesse]

Well, this JavaUtil class is in the jbang CLI, so this code here is exactly where that instance using jbang config is created.

[quintesse]

NB: If you look a bit lower in the createProvider() method you see it references config, which is the jbang config. The missing part I mentioned in our chat is exactly that: tying together the config with the instance creation :-)