* Move the tests out to their own tasks
* Revert change
* Lets try this
* Actually reference to the tests
* Lets try this
* lets try this too?
* this one?
* Manually define them :(
* Formatting
* Add the node command
* Fix machine learning and address comments
* Setting up tests on import extension
* -Added API wrappers for all the azdata and vscode APIs to make them easily mockable
-Added some unit tests for the import extension
-Some code logic separations
* -added code report for the import extension in ci
* Did some more code refractoring
* -Added json report generation
* updated vscodetestcoverage to latest version in import extension.
* -remove duplicate codecoverageConfig.json
Converted `test-extensions-unit.bat` to javascript to add a small QoL improvement that I think people will find useful: specifying which extension(s) you want to run tests for instead of commenting out lines of a script.
In addition to existing behavior being mostly preserved (node test-extensions-unit.js defaults to running all unit tests), you can specify one or more:
```
node test-extensions-unit.js sql-database-projects
node test-extensions-unit.js sql-database-projects schema-compare
```
