Initial CodeTours for contributing to VS Code and Visual Studio extensions

[TMA-2]

For issue #129 - These are more or less placeholder CodeTours consisting of the content on the Wiki for building the extensions, but associated with files and directories where applicable. Also, a VSCode workspace, which may not be totally necessary, but having some VSCode configurations to assist in getting a similar environment set up would certainly help me.

[adamdriscoll]

This is looking good to me! Let me know if you feel like this is ready to merge.

[TMA-2]

This is looking good to me! Let me know if you feel like this is ready to merge.

Thanks very much — I'm relatively new to using git so I wasn't sure I got it right (as evidenced by the many needless back-and-forth commits beforehand...).

I think one thing might need updating, though:

• The Visual Studio tour, step 11: PowerShellTools.MSBuild might need to actually reference PowerShellToolsPro.MsBuild? I could be mistaken, you would you know your own repo but wanted to verify.

Also, I generated some PlatyPS help files for most of the PowerShellProTools.VSCode module as they seem to lack any help content. Besides finishing those and generating MAML help, would it be worth adding in-line XMLDoc documentation to the cmdlet files, i.e. SetStatusBarMessageCommand.cs?