Issue 492 deploytoazurebutton

[rumdood]

This is the initial PR to start the process of adding a DEPLOY TO AZURE button to the documentation (#492)

This is a straightforward addition of a "deploy" folder off of the root of the repository, containing an ARM template for deploying DasBlogCore to an Azure App Service. There will be two follow-up PRs:

• One to the Wiki pages to add the DTA button and instructions on how to configure it.
• One to update the main project README with the DTA button and a link to the deployment instructions in the Wiki.

This ARM template will allow the user to deploy a single App Service using:

• Windows
• 64-bit Process
• Git-Deployment

The user has the ability to change the following settings when deploying the template:

• Name of the application/site
  • The name provided by the user will automatically have a suffix of 13 random characters added in order to ensure uniqueness of the subdomain/host. This is necessary because there is no way to check for uniqueness prior to deployment and the deployment doesn't not roll back the hosting plan if it fails due to a name collision.
• Name of the hosting plan
  • If an existing hosting plan name is used, the AppService will be added to the existing plan. If the plan does not exist, it will be created
• SKU (defaults to B1)
• Worker Size (defaults to 0/small)
• Repo URL
  • This is the URL of the git repository where the DasBlogCore project to be deployed is stored. It defaults to https://github.com/poppastring/dasblog-core.git to deploy from the root repository, but the user can point this to their own fork of the core project.