1.0 being an integer is not optional behavior.

Move the tests from zeroTerminatedFloat.json to type, since
as of draft 6, this behavior is required, and required to
consider such numbers to be integers.

See json-schema-org/json-schema-spec#898 for some discussion,
not of the underlying requirement, simply of this file being
in the wrong place.

Author: Julian

tests/draft2019-09/optional/zeroTerminatedFloats.json

@@ -8,6 +8,11 @@
                 "data": 1,
                 "valid": true
             },
+            {
+                "description": "a float with zero fractional part is an integer",
+                "data": 1.0,
+                "valid": true
+            },
             {
                 "description": "a float is not an integer",
                 "data": 1.1,

tests/draft2019-09/type.json

@@ -8,6 +8,11 @@
                 "data": 1,
                 "valid": true
             },
+            {
+                "description": "a float with zero fractional part is an integer",
+                "data": 1.0,
+                "valid": true
+            },
             {
                 "description": "a float is not an integer",
                 "data": 1.1,

tests/draft6/optional/zeroTerminatedFloats.json

@@ -8,6 +8,11 @@
                 "data": 1,
                 "valid": true
             },
+            {
+                "description": "a float with zero fractional part is an integer",
+                "data": 1.0,
+                "valid": true
+            },
             {
                 "description": "a float is not an integer",
                 "data": 1.1,