Make NewAzureDeployment param validation consistent with SetAzureDeployment

- SetAzureDeployment only checks if the CurrentStorageAccount is set if the package needs to be uploaded to storage
- NewAzureDeployment always throws if CurrentStorageAccount is set regardless of whether the package needs to be uploaded to storage
- This change makes NewAzureDeployment consistent with the behavior of SetAzureDeployment

Author: Ryan Lewellen

src/ServiceManagement/Compute/Commands.ServiceManagement/HostedServices/NewAzureDeployment.cs

@@ -123,6 +123,11 @@ public virtual void NewPaaSDeploymentProcess()
             }
             else
             {
+                if (string.IsNullOrEmpty(storageName))
+                {
+                    throw new ArgumentException(Resources.CurrentStorageAccountIsNotSet);
+                }
+
                 var progress = new ProgressRecord(0, Resources.WaitForUploadingPackage, Resources.UploadingPackage);
                 WriteProgress(progress);
                 removePackage = true;
@@ -265,11 +270,6 @@ protected virtual void ValidateParameters()
             {
                 this.Label = this.Name;
             }
-
-            if (string.IsNullOrEmpty(this.CurrentContext.Subscription.GetProperty(AzureSubscription.Property.StorageAccount)))
-            {
-                throw new ArgumentException(Resources.CurrentStorageAccountIsNotSet);
-            }
         }
     }
 }