Drop Support for type as array of strings

[BelfordZ]

The first json schema spec draft included type as array. It did not include anyOf, allOf, oneOf. These were never options at the time.

Now that they do exist, we have a feature multiplicity violation. That is, we have 2 ways of achieving ultimately the same thing, which is a mistake in any DSL.

What would change?

we would make the top level JSONMetaSchema schema into a oneOf: [ { type: "object" }, { type: "boolean" } ]
generated typings will now reflect the ability of a schema to be a boolean.

thats all. No user facing changes. All downstream libraries already support this change.