Improve Extension Authoring Experience with new Build Tasks and Launch Configs

[JustinGrote]

PR Summary

Updates the build tasks and launch configs to:

• Massively shorten inner loop development on typescript features by using incremental watch configs
• Integrate linting process into vscode so that lint errors are surfaced in the IDE prior to CI commit or manual lint run
• Enable semicolons for typescript actions like auto-formatting since the current ESLint profile requires them.
• Provide a launch test task for isolated testing separate from developer's profile
• Provide extension launchers for interactive debugging of the extension in either the developer's profile, a temp throwaway profile, or an isolated but persistent profile
  

Testing

1. Open the workspace file

2. Run ./build at least once (integrated PSES watch builds and auto-attach debugging is future PR)

3. Click the Test Extension Launch Task and note the vscode instance that starts does not use your personal settings

4. Click the Launch Extension Task and note the launched extension has your settings. First run may take a while but future starts should be near-instant. Also note that there are watch tasks now running for both tests files and build files and will auto-update every time you save a change and have a status indicator to the right.
   

5. Click the Launch Extension - Isolated Profile task and note the vscode window is isolated. Change your theme and launch again, observe that theme persisted but did not change developer's personal settings.

6. Repeat with Launch Extension - Temp but note the theme change does not persist.

7. Insert an intentional error into a .ts file and try to run a launch config. An error will appear saying that errors ocurred and will take you straight to the errors.
   

PR Checklist

Note: Tick the boxes below that apply to this pull request by putting an x between the square brackets.
Please mark anything not applicable to this PR NA.

• PR has a meaningful title
• Summarized changes
• PR has tests
• This PR is ready to merge and is not work in progress
  • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready

[andyleejordan]

I like it!