Move script file.

The HomeScrum JavaScript source was lumped in with the 3rd party library sources.  This made our code harder to find.
Moving it to its own directory solved that problem.
Update 3rd party libraries.
Update BCL version used in test project.
Add qunit to the project.
Add a simple meaningless test.

This test just makes sure we have everything installed and working before we begin the actual tests.
Add basic module structure to test.
Test initial state of button.
Test the initial state of the elements in the list.
Test the toggling of the show/hide button.
Add local storage tests.
Start adding work item editor tests.
Add the instance name to the connect string.

It did not work on my surface without the instance name.
The instance name should be the same on all three development machines, so this should not cause an issue.
If this is not the case, I will have to look at a different solution.
Merge branch 'feature/AddJavaScriptUnitTests' of https://github.com/kensodemann/HomeScrum into feature/AddJavaScriptUnitTests
Define basic structure that will be followed.
Change name of myUIExtensions.js to utilities.js.

I am planning on adding a couple of functions to this.
Switch utilties JS to use the module pattern.

This is simply an organizational move that should eventually help keep the code organized as it grows.
Put the show/hide button code into its own private module.
Add the syncHiddenElement function to utilities.

This is used in a few different views, and thus needs to be somewhere common.
Use common Sync Hidden function.
Make Editor into a module.