Fix provision errors and add Provision-All and update Readme

[hanzzhang]

connects to #226

[lbrader]

2 Issues

1. Name collision for EventHub Connectioni string.
   This occurred in AzureServiceBus.ps1 New-EventHubIfNotExists function. When it returns from that function to the Provision-ColdStorageEventProcessor.ps1 function. The EventHubInfo now contains 2 strings in the property ConnectionStrings, which causes an XML error when writing out to the config file. To fix this, I gave our connection string a unique name and no more collision.
2. We are creating Web edition database for our SQL scenario. The Web edition database will be phased out Sept 15. Haven't fixed this item. Did create a issue with a link to how to create the SQL Base version, which is the recommended solution. #229

[lbrader]

Follow up note:

• Tried to rename EventHubInfo to see i could avoid this issue with Service Bus. That didn't work.
• See if there existed an EventHubInfo from Service Bus. Didn't find any objects.

Still a bit puzzled why we are getting this collision on the ConnectionString property in this object.