Remove default value for meta-schema

With default values now having implication for both assertions
and annotation collection, it no longer makes sense to have
a default value for subschemas.

Keywords such as "additionalProperties" now collect annotation
information based on the instance properties to which thier
subschema(s) are applied.  This means that a subschema of true
will cause a property to appear in the annotation, while an
absent subschema will not.  Therefore, a default of true does
not match the annotation collection behavior and is not accurate.

Additionally, as written this has always been problematic, as
it claims a default true value for "not", which would in fact
cause all schemas without "not" to fail.

Author: handrews

schema.json

@@ -106,8 +106,7 @@
             "anyOf": [
                 { "$ref": "#" },
                 { "$ref": "#/$defs/schemaArray" }
-            ],
-            "default": true
+            ]
         },
         "maxItems": { "$ref": "#/$defs/nonNegativeInteger" },
         "minItems": { "$ref": "#/$defs/nonNegativeIntegerDefault0" },
@@ -162,13 +161,12 @@
         "format": { "type": "string" },
         "contentMediaType": { "type": "string" },
         "contentEncoding": { "type": "string" },
-        "if": {"$ref": "#"},
-        "then": {"$ref": "#"},
-        "else": {"$ref": "#"},
+        "if": { "$ref": "#" },
+        "then": { "$ref": "#" },
+        "else": { "$ref": "#" },
         "allOf": { "$ref": "#/$defs/schemaArray" },
         "anyOf": { "$ref": "#/$defs/schemaArray" },
         "oneOf": { "$ref": "#/$defs/schemaArray" },
         "not": { "$ref": "#" }
-    },
-    "default": true
+    }
 }