Updated Bootstrap.java to better handle launch targets, we know split the setting up and launching in two spots, to allow more room for early services from boostrap to do their things... such as LoggerProviders

Author: RealMangorage

src/main/java/org/mangorage/bootstrap/Bootstrap.java

@@ -80,9 +80,11 @@ public static void main(String[] args) throws Throwable {
         LOGGER.info("Launching target: " + launchTarget);
 
         try {
-            final var launchLayer = launchTargetMap.get(launchTarget).launch(moduleLayer, parent, args);
+            final var target = launchTargetMap.get(launchTarget);
+            final var launchLayer = target.setup(moduleLayer, parent, args);
             if (launchLayer != null) {
                 DefaultLoggerFactory.load(launchLayer); // Load the providers this layer has!
+                target.launch(launchLayer, args);
             }
         } catch (Throwable t) {
             LOGGER.error("Error during launch target execution: " + launchTarget, t);

src/main/java/org/mangorage/bootstrap/api/launch/ILaunchTarget.java

@@ -4,7 +4,11 @@ public interface ILaunchTarget {
     String getId();
 
     /**
+     * Set up the module layer and everything!
+     *
      * @return The ModuleLayer that was created!
      */
-    ModuleLayer launch(ModuleLayer bootstrapLayer, ModuleLayer parent, String[] args) throws Throwable;
+    ModuleLayer setup(ModuleLayer bootstrapLayer, ModuleLayer parent, String[] args) throws Throwable;
+
+    void launch(ModuleLayer moduleLayer, String[] args);
 }