Warning for Special Characters and Ability to Run Queries As File

This was the fix for the defect about the SDK being able to handle special characters in query strings that are passed to templeton (Defect 3076743). This fix will wait on the corresponding SDK fixes to be checked in as well.

Powershell Changes:
1.) List Warnings about using query strings so that we can steer customers away from using queries strings. We have found some special characters that can't be used, but there may be other limitations, so it's best to always throw a warning.

2.) Provide plumbing from Powershell into SDK to be able to -RunAsFileJob. This won't work without the corresponding SDK fix, but the SDK will catch any errors if they try to RunAsFileJob and are connected to the cluster directly instead of the subscription

3.) Remove the Special Character check here as it's already in the SDK and if we discover more special characters we would be having to list them both in the SDK and powershell. With the SDK fix, it throws a nice error if there's a known special character in the query (looks like below)

Start-AzureHDInsightJob : Query contains restricted character :'%'.
Please submit job as a File job or set RunAsFileJob to true.