* package migration for @microsoft packages and T2
* Remove stale comment
* Add registerAzureUtilsExtensionVariables(ext) call before AppService
* Alphabetize
* Comments to fix loadMore if paging gets fixed
* Add tests for deploying CSharp and JavaScript projects
* Modify the code according to FTE's comments
* Solve the file conflict in the package.json
* Modify the code according to FTE's comments
* Modify file configuration information in package.json
* Modify the code according to FTE's comments
* Modify the code according to FTE's comments
* Modify the code according to FTE's comments
* Adjust the code format
* Update the path to match docker repo
* Update code according to the comments
* Update code according to the comments
* Update code according to the comments
* Update code according to the comments
1. Actually verify the settings passed in
1. Don't use "vscode.command.executeCommand" becuase that swallows exceptions
1. Validate that there is a test for every "Verified" template
As opposed to overwriting the "tasks.json" and "launch.json" files if they already exist, we will just add our config to those files. I think this is especially necessary when users have their Functions project in a sub directory because that means they could have debug configs for other projects in other sub directories.
I ran into two bugs while testing the release candidate:
1. The tasks.json we generate is meant to work if someone pushes their project to GitHub and clones it on a different OS. That wasn't the case for our "pipInstall" task because it always used the path separator from the _original_ OS
1. Windows users with their terminal set to bash would fail to debug
In order to fix, I ended up doing quite a bit of refactoring of venvUtils and added several tests to cover all the weird edge cases. Here's the list of terminals: https://code.visualstudio.com/docs/editor/integrated-terminal#_configuration
I also removed the logic to install "pylint" by default. It's just another command that could fail and it slows down project creation. We originally did it because the Python extension was super annoying and prompted you to install pylint every time, but now they at least have a "Don't show again" button. Fixes#814
Nathan
Eric Jizba
v-wuzhai
Tyler James Leonhardt