Convert sln to use NuGet Package Restore

This also has the effect of moving the NuGet packages directory from root to the sln directory (under /src).  However, now src/packages will no longer be under source control.
Remove root level \bin directory

Originally it was more convenient to copy all binaries from the various VS project bin folders to a root-level bin folder.  However, since this project is ultimately going to be packaged for NuGet, this is no longer necessary.
Rename solution file

In preparation for the namespace rename of FluentSiteMap -> TS.FluentSiteMap.
Rename namespace FluentSiteMap -> TS.FluentSiteMap
Create LICENSE file
Add Buildage submodule

This involves making copies of the Buildage sample input files and customizing them per the Getting Started instructions as well as modifying the solution files to use the new generated GlobalAssemblyInfo.cs.
Since the solution already had a GlobalAssemblyInfo.cs, it was removed since it no longer needs to be kept under source control.
Replace TS.Testing lib with TS.NUnitExtensions package

TS.Testing was the predecessor to TS.UnitExtensions, which is now a NuGet package.
Swapping out the library also requires updating using statements in the code to use the new namespace (TS.NUnitExtensions).
Minor code and comments clean-up after code review
Rename FluentSiteMap project to FluentSiteMap.Core

Part 1 of 2 for the rename.  Next we need to change the assembly name to TS.FluentSiteMap.Core.
Rename FluentSiteMap.Core's assembly name to *.Core

Finishing the rename of the project and assembly.
NOTE: The core namespace has not changed: TS.FluentSiteMap
Modify package metadata for final packaging

Inluding the addition of the main package (TS.FluentSiteMap), which is really just changes for a web project and references .Core.
Update to latest Buildage version: 8f3d07e2