General tidy up

Complete a general tidy up of the solution:

  - Ignore some tests that should be integration tests.  I can't work out how these OAuth tests ever worked, given that they hit http://localhost/ with a POST.
  - Remove an empty Infrastructure folder.
  - Delete the sample ApiController.
  - Move existing Facts to the correct namespace.
  - Remove unused usings.
  - Remove an unused using.
  - Update NCrunch solution file.
Pull side bar out into a partial view.
Add models for the side bar, and a controller

A SideBarSection denotes a particular group of links.  A SideBarLink
denotes a single link within the side bar.
Introduce a SideBarProvider class

The reponsibility of inheritors of this class is to do the work of
fetching the necessary information and building the tree of side bar
sections and links.
Add initial tests for the side bar controller.
Side bar should not render if it has no links.

Verify this with a test.
Rename SideBarProvider -> SideBar
Add Ninject Factory extension.
Introduce a SideBarFactory interface.

This interface is implemented on the fly by Ninject to create the required
instance of the SideBar, currently hard-bound to ConcertsSideBar.  It
removes part of the Abstract Factory pattern boiler plate, but it
(obviously) doesn't provide the logic required to bind a specific side bar
based on the requested action's controller.
Resolve the sidebar by the controller name.

Add the requesting controller to the route data, and then pull it out of
the route data to construct an appropriate side bar object for the page.

The SideBarFactory is currently combining the concerns of a
ConcertsSideBarFactory, an EmptySideBarFactory, and a
SideBarFactoryFactory (deciding which factory to use).  This needs to be
rectified, probably once I've got the persistence sorted.
Merge branch 'feature/sidebar-ActionParameter' into feature/sidebar
Merge branch 'feature/sidebar' into develop
Open source the project under the MIT licence.

Publish the licence in LICENCE.md, and refer to it from the readme.
Add a Powered By RavenDB logo

Re-add the default Site.css stylesheet that came with the Web API project,
but strip out all the styles I don't need or want so the site maintains
its current Bootstrap default styling.  Remove the associated images too.
Add RavenDB to the Web API project.

Pull in via NuGet.  I'm using the unstable pre-release build at the moment
to avoid versioning conflicts with Newtonsoft.Json.  Raven is included in
its embedded form, so I don't have to worry about setting it up on a
server and connect to it from Azure.
Initial wire-up of Raven.

Add an IDocumentSessionFactory that can be provided to controllers to
obtain an IDocumentSession.  Hook this into the Concerts controller as an
experiment.  For the moment, these two types are mocked in the Concerts
controller's tests, but should be swapped out for an in-memory database.
Move to in-memory tests for ConcertsController.

I'm not sure how much I like this at the moment: my unit tests are now
integration tests, BUT you shouldn't mock types you don't own.  Perhaps I
should put a thin wrapper around Raven's IDocumentSession.
Git-ignore the RavenDB data directory.
Add IDocumentSessionFactory to SidebarController.

It doesn't do anything with it yet, but it will do...
Re-add the RavenDB Embedded reference.

This seems to have been removed somewhere in a previous commit.