#5 - Modify Femah Admin UI to use API backend.
- Bundled all backboine views and models in to one JS file with consistent namespacing to make navigation of this relatively small app a bit easier.
- Refactored app.js to perform fetch of collections
- Refactored FemahHtpHandlerUsingApi to make the RenderFeatureRow method redundant, all row logic being generated by backbone implementation utilising templates.

TODO -
NUnit test for changes to HttpHandler
Jasmin tests for backbone
	- test models with mocked data?
#5 - Modify Femah Admin UI to use API backend.
- Removed temporary debugger flag in backbone template
- Removed later backbone, underscore and jquery versions as I'll be damned if I can get anything working with them properly.
- Refactored the Femah.FeatureSwitchesView to utilise real collection data of FeatureTypes from the API as opposed to a hard-coded array of test data.
#5 - Modify Femah Admin UI to use API backend.
- Removed the now redundant RenderFeatureRow() method from the FemahHttpHandlerUsingApi HttpHandler.
- Commented out backbone views I don't believe we have use for.
#5 - Modify Femah Admin UI to use API backend.
- Implemented HTTP POST with the backbone Femah.FeatureSwitch model to replace the Femah.Core.Femah.EnableFeature() method call within the ProcessRequest() method.
- Reintroduced more current versions of Backbone JS and Underscore libraries.