Upgrading to everit json-schema 1.14.4 breaks Kafka Connect conversions

[rayokota]

When converting a JSON schema to a Kafka Connect schema, field names were indexed by the order in which they were returned from CombinedSchema.getSubschemas() here. This order changed in everit-org/json-schema#498. That new change also relies on hashCode, which means the order is not guaranteed to be deterministic across JVM executions.

A possible fix is everit-org/json-schema#522, which guarantees the subschemas are always returned in insertion order, which is deterministic for a given JSON Schema, and across JVM executions.

One of the tests that breaks due to everit-org/json-schema#498 is here.