Optional tests for no $schema (2019-09+)

minLength is identical across all drafts, and highly unlikely
to ever change, so regardless of how an implementation chooses
to process this schema, if it processes it at all the behavior
should be consistent.

Also, TIL that "type" has *not* always been the same - in the first
few drafts it was always an array of types *or schemas*!  While
we don't even have test suites for those drafts, it seemed better
to use a keyword that has never changed.

Author: handrews

tests/draft2019-09/optional/no-schema.json

@@ -0,0 +1,26 @@
+[
+    {
+        "description": "validation without $schema",
+        "comment": "minLength is the same across all drafts",
+        "schema": {
+            "minLength": 2
+        },
+        "tests": [
+            {
+                "description": "a 3-character string is valid",
+                "data": "foo",
+                "valid": true
+            },
+            {
+                "description": "a 1-character string is not valid",
+                "data": "a",
+                "valid": false
+            },
+            {
+                "description": "a non-string is valid",
+                "data": 5,
+                "valid": true
+            }
+        ]
+    }
+]

tests/draft2020-12/optional/no-schema.json

@@ -0,0 +1,26 @@
+[
+    {
+        "description": "validation without $schema",
+        "comment": "minLength is the same across all drafts",
+        "schema": {
+            "minLength": 2
+        },
+        "tests": [
+            {
+                "description": "a 3-character string is valid",
+                "data": "foo",
+                "valid": true
+            },
+            {
+                "description": "a 1-character string is not valid",
+                "data": "a",
+                "valid": false
+            },
+            {
+                "description": "a non-string is valid",
+                "data": 5,
+                "valid": true
+            }
+        ]
+    }
+]