AppDomain Robot & NuGet Functionality

Items of note:
- Some modifications to Program.cs to run the robot in another AppDomain
- NuGetScripts.cs contains base level NuGet functionality
- Updates to the INI template to include some NuGet-specific features
- Some changes in ConsoleAdapter to get it to properly shutdown when resetting
- There are no tests at the moment. VS really doesn't seem to like referencing the mmbot project directly. It acts like it can't find it. Additionally I haven't really extracted most things like accessing NuGet repositories out behind an interface, so unit testing them wouldn't be super-pretty at the moment, since they're relying on actual endpoints instead of injected (and mockable) objects. (I previously cited some way out of date Phil Haack article--turns out it wasn't relevant.)

Things the NuGetScripts support:
- Add/Remove a package source (NuGet package repository)
- Update/Install packages
- Add/Remove/List package aliases

A small test case:
Make a NuGet package with a script in it that just returns the version of the assembly that contains the script. 
Build it, package it.
Set a local folder up as a package source in the INI file and use "mmbot update PACKAGE_NAME" to install it.
Increment the version number of your package, build and package again. (Make sure to drop it in the folder with the other version.)
Run your script that gets the assembly version.
In mmbot, use "mmbot update PACKAGE_NAME" to get the updated version.
Run your script that gets the assembly version.
Your version should be incremented.