Fix usage of "not"

Constructs such as:

type: object
not:
  type: object

will always fail, so remove the type inside the not.

The "not" usage around "^x-" patterns for responses is
unnecessary, as the existing

patternProperties:
    "[1-5]..."
additionalProperties: false

prevents all property that do not start with 1, 2, 3, 4, or 5
from being allowed already.

Author: handrews

schemas/v3.0/schema.yaml

@@ -666,14 +666,8 @@ definitions:
         oneOf:
           - $ref: '#/definitions/Response'
           - $ref: '#/definitions/Reference'
-      '^x-': {}
     minProperties: 1
     additionalProperties: false
-    not:
-      type: object
-      patternProperties:
-        '^x-': {}
-      additionalProperties: false
 
 
   SecurityRequirement:
@@ -1250,20 +1244,16 @@ definitions:
       - $ref: '#/definitions/BearerHTTPSecurityScheme'
 
   NonBearerHTTPSecurityScheme:
-    not:
-      type: object
-      properties:
-        scheme:
-          type: string
-          enum:
-            - bearer
     type: object
     required:
       - scheme
       - type
     properties:
       scheme:
         type: string
+        not:
+          enum:
+            - bearer
       description:
         type: string
       type: