Adding unit tests - READY :D

[katelynienaber]

This PR includes the following:

• Test runner, so you can start the unit tests from the extension host

Some minor Lint fixes, where I saw them:

• Ordering object properties alphabetically
• Trailing commas

Unit tests for:

• Profiles refresh function
• Profiles getEndevorCliProfileManager function
• List (view) action for elements (browseElement)
• retrieveElement
• retrieveElementWithDependencies
• createNewConnection

I did not test promptCredentials because it is currently not called anywhere in the extension...

[Alexandru-Dumitru]

Thanks for working on this. Some things I noticed:

• we can keep tests close to the functionality they test, so we don't need src/__tests__/__unit__, but we can put them in /functionality/__tests__/. Tests for functionality under src can obviously go in src/__tests__/ (not really mandatory, just a thought)
• I tried to run the tests both from npm run test:no-vscode and the debugger, and didn't work for me. I got the following error for all new test files:

    Cannot find module 'vscode' from 'src/__tests__/__unit__/service/profiles-test.ts'  

      26 |  */
      27 | 
    > 28 | import * as vscode from "vscode";

• also, once we add meaningful tests, we can remove the fake ones at src/__tests__/sample-test.ts and src/__tests__/sampletests folder.
• lastly, fixing linting stuff adds a little bit of noise to the review process :( . We are also going to replace linting tool within other PR (so rules will change). No big issue here
• Ran the extension manually from the branch and it worked fine for me (manual testing) 👍

[zdmullen]

Hey, I got several errors when I ran the tests. Here are some screenshots:

[katelynienaber]

@Alexandru-Dumitru @zdmullen Okay so unit tests should be fixed now.

[Alexandru-Dumitru]

Thanks Katelyn! Works well for me. 👍

I am going to approve it but I do have one remark going forward. The reason why we use Mocha and vscode-test is to test the integration with VS Code. Having to extensively mock vscode stuff to make Jest tests work is something that we should strive to avoid. This means that through an ongoing refactoring process we should localize as much as possible the usage of vscode module so that it doesn't create this kind of impediment in tests.