Update In Place

This pull requests represents the update-in-place functionality. 

Components that were added:

Staging buckets on S3:
New buckets were added on S3 for staging builds and signature files. The upload scripts were given an additional flag to allow you to direct to staging or production. Debug builds of Dynamo will pull from staging based on an #if DEBUG that sets the end point.

Signature file support:
We now download a signature file at the same time that we download the update installer. This signature file is used to validate the installer using a public key.

DynamoCrypto Library:
Methods for finding certificates in certificate stores, extraction of public or private keys, and verification of installers. A certificate containing our public key (Dynamo.cer) is now in the DynamoCrypto directory and is placed in the main build directory. When the user first installs an update, this certificate will be registered in their "current user" certificate store.

InstallDynamo console application: 
Uses DynamoCrypto methods to verify an installer against a signature file using public key before beginning install.

SignDynamo console application:
Uses DynamoCrypto methods to generate a signature file for Dynamo based on a private key. In order to test this functionality you must install the private key on your machine, or test through the CI (where the private key has been installed). The signature file is placed in the same directory as the installer and is uploaded to S3.

Instructions for how to register the certificate for generating signature files is here (https://github.com/DynamoDS/Dynamo/wiki/Signing-and-Uploading-Installers).

@lukechurch Please review. This is really big. I'd be happy to sit down and talk it through.
@pboyer I might also need your input on amazon permissions. I can't seem to get the downloads to work without making each individual file "public". Can I make a whole bucket public?

Worth noting here that this algorithm only works with DSA?