remove wrong default error response (#8923)

Have discussed the recommendation of providing Default with correct error schema in order to surface error message to customer. Without it, if the error message format differs from standard cloud error, user of SDK would only get a generic CloudException with error status code but no detailed error message. Adding default with schema LATER would be a SDK breaking change.

Monitor team indicated understanding of the issue and with urgent JEDI requirement and opt for this approach.

Author: arolshan

specification/monitor/resource-manager/Microsoft.Insights/preview/2019-10-17-preview/privateLinkScopes_API.json

@@ -47,12 +47,6 @@
           }
         ],
         "responses": {
-          "default": {
-            "description": "Error response describing why the operation failed.",
-            "schema": {
-              "$ref": "../../../../../common-types/resource-management/v1/types.json#/definitions/ErrorResponse"
-            }
-          },
           "200": {
             "description": "A list containing 0 or more Azure Monitor PrivateLinkScope definitions.",
             "schema": {
@@ -86,12 +80,6 @@
           }
         ],
         "responses": {
-          "default": {
-            "description": "Error response describing why the operation failed.",
-            "schema": {
-              "$ref": "../../../../../common-types/resource-management/v1/types.json#/definitions/ErrorResponse"
-            }
-          },
           "200": {
             "description": "A list containing 0 or more Azure Monitor PrivateLinkScope definitions.",
             "schema": {
@@ -128,12 +116,6 @@
           }
         ],
         "responses": {
-          "default": {
-            "description": "Error response describing why the operation failed.",
-            "schema": {
-              "$ref": "../../../../../common-types/resource-management/v1/types.json#/definitions/ErrorResponse"
-            }
-          },
           "200": {
             "description": "Successful request when deleting a Azure Monitor PrivateLinkScope."
           },
@@ -169,12 +151,6 @@
           }
         ],
         "responses": {
-          "default": {
-            "description": "Error response describing why the operation failed.",
-            "schema": {
-              "$ref": "../../../../../common-types/resource-management/v1/types.json#/definitions/ErrorResponse"
-            }
-          },
           "200": {
             "description": "An Azure Monitor PrivateLinkScope definition.",
             "schema": {
@@ -215,12 +191,6 @@
           }
         ],
         "responses": {
-          "default": {
-            "description": "Error response describing why the operation failed.",
-            "schema": {
-              "$ref": "../../../../../common-types/resource-management/v1/types.json#/definitions/ErrorResponse"
-            }
-          },
           "200": {
             "description": "Successful request when creating or updating a Azure Monitor PrivateLinkScope. The updated PrivateLinkScope is returned.",
             "schema": {
@@ -264,12 +234,6 @@
           }
         ],
         "responses": {
-          "default": {
-            "description": "Error response describing why the operation failed.",
-            "schema": {
-              "$ref": "../../../../../common-types/resource-management/v1/types.json#/definitions/ErrorResponse"
-            }
-          },
           "200": {
             "description": "Updating the Azure Monitor PrivateLinkScope's tags was successful. PrivateLinkScope tags are updated and returned with the rest of the PrivateLinkScope's object properties.",
             "schema": {