Add launch configuration for also debugging MicroProfile extension

- It is sometimes necessary to debug both the Quarkus and MicroProfile
  project folders at once
- extensionDevelopmentPath option may be provided multiple times,
  permitting the debugging of multiple extensions at once
- The new configuration assumes a contributor has placed the
  vscode-quarkus & vscode-microprofile project folders under the same
  folder
- Update CONTRIBUTING document

Signed-off-by: Roland Grunberg <rgrunber@redhat.com>

Author: rgrunber

.vscode/launch.json

@@ -21,6 +21,24 @@
       ],
       "preLaunchTask": "npm: watch"
     },
+    {
+      "name": "Run Extension with MicroProfile sources",
+      "type": "extensionHost",
+      "request": "launch",
+      "runtimeExecutable": "${execPath}",
+      "args": [
+        "--extensionDevelopmentPath=${workspaceFolder}",
+        "--extensionDevelopmentPath=${workspaceFolder}/../vscode-microprofile"
+      ],
+      "env": {
+        "VSCODE_REDHAT_TELEMETRY_DEBUG": "true"
+      },
+      "outFiles": [
+        "${workspaceFolder}/dist/**/*.js",
+        "${workspaceFolder}/../vscode-microprofile/dist/**/*.js"
+      ],
+      "preLaunchTask": "npm: watch"
+    },
     {
       "name": "Extension Tests",
       "type": "extensionHost",

CONTRIBUTING.md

@@ -266,6 +266,9 @@ In addition to `npm run build`, there are two more build scripts:
 "Launch Extension (vscode-quarkus)" at the top left.
 ![](images/runExtension.png)
 
+If the extension depends on changes from the MicroProfile extension that are not released into the Marketplace, or only available locally, select and run "Run Extension with MicroProfile sources" at the top left.
+![](images/runExtensionWithMicroProfile.png)
+
 ### Testing vscode-quarkus
 There are two types of tests written for vscode-quarkus:
 the [integration tests](https://code.visualstudio.com/api/working-with-extensions/testing-extension) and the UI tests.