Document release process

We need to document the process for releasing from this repo into the Azure Quickstarts repo. Here's an initial set of ideas:

We aim to release every 2nd and 4th Wednesday

## Version numbering
Version numbers are x.m.i, where x = major version number, m = month number, i = iteration number (e.g. 1.1.2 is the version from the 4th Wednesday of the month). If interim releases are needed (e.g. security patch) they will be indicated with an addition digit, e.g. x.m.i.y, where y is an incremental number

## Release Preparation (1st and 3rd Wednesday)
1. validate all issues with milestone of next release. Move out issues that are going to slip.
1. Merge dev branch into releasecandidate branch
1. Increment version numbers in dev branch
1. test and validate releasecandidate branch

## Release Process (2nd and 4th Wednesday)
4. Update URLs for deploy button and script locations
5. Update version numbers
5. cp code to azure/quickstarts fork
6. issue pull request
7. validate against best practice
8. merge into quickstarts