Fixes issue with migrations running with a Decimal column:

The logic would produce incorrect syntax.
Fixed the default string column for sql server, made them all consistent.
Moved ctor logic for shared sql syntax providers to the base class.
Created formatted Decimal column definitions so that a custom precision/scale works.
Set the migration to use the default precision/scale values.
Removes the pattern validators because they don't do anything... due to the fix-number directive which has it's own issues but we won't solve those now.

src/Umbraco.Web.UI.Client/src/common/directives/validation/valregex.directive.js

@@ -40,7 +40,7 @@ function valRegex() {
 
             var patternValidator = function (viewValue) {
                 //NOTE: we don't validate on empty values, use required validator for that
-                if (!viewValue || regex.test(viewValue)) {
+                if (!viewValue || regex.test(viewValue.toString())) {
                     // it is valid
                     ctrl.$setValidity('valRegex', true);
                     //assign a message to the validator

src/Umbraco.Web.UI.Client/src/views/propertyeditors/decimal/decimal.html

@@ -1,7 +1,6 @@
 <div class="umb-editor">
     <input name="decimalField" 
            type="number"
-           pattern="[0-9]+([,\.][0-9]+)?"
            class="umb-editor umb-number"
            ng-model="model.value"
            val-server="value"

src/Umbraco.Web.UI.Client/src/views/propertyeditors/integer/integer.html

@@ -1,7 +1,6 @@
 <div class="umb-editor">
     <input name="integerField"
            type="number"
-           pattern="[0-9]*"
            class="umb-editor umb-number "
            ng-model="model.value"
            val-server="value"