Created a Powershell script to package an official Ghost release for Azure, reducing 8 steps to 2.
Also changed the Azure configuration so that Ghost is secure by out-of-the-box, e.g. the intial sign-up / admin section is now https.

Also:
- Removed previous submitted azure package from /binaries folder. No longer required as previous versions can be generated by the Powershell script.
- We don't want our share our secret *.publishSettings or have .zip *.sha1 files that are created/used by the Powershell scripts.
- Added a Powershell script to deploy a package to Azure, uses Web Deploy and Parameters used for testing the Azure package using webdeploy
- Updated Readme.md with how to package a release using the Powershell script and testing on Azure.
- Added external dependency on [Ionic.Zip](http://dotnetzip.codeplex.com/) (`Ionic.Zip.Reduced.dll`) as the `System.IO.Compression.FileSystem` created an archive that wasn't able to be read by Web Deploy<sup>1</sup> (and I assume by the Azure Web App Gallery). This was meant to be in the previous pull-request, however was accidentally lost when squashing the commits for PR.

- Clean-up temporary packaging files at end of script, unless` -Debug` flag is specified.
- Added `Pop-Location` if there was an error to return host to starting directory.
- `UTF8` output from `npm` was causing the Powershell console to error <sup>2</sup> if using the `-Verbose` flag, so now the script strips out `UTF8` characters using regex replace. Interesting the Powershell ISE handled the error, which is why I didn't notice it before.

Changes to the Deploy.ps1 script.
- Removed SUCCESS message as it was misleading. It would print regardless of the deployment status.

<sup>1</sup>`Error Code: ERROR_EXCEPTION_WHILE_CREATING_OBJECT`
<sup>2</sup> `The Win32 internal error "A device attached to the system is not functioning" 0x1F occurred while writing to the console output buffer at the current cursor position.`