6.2.3 patch release is not compatible with 6.2.2

[dr3s]

Before version 6.2.3, the schema registry client was registering corrupted, invalid protobuf schemas into the registry which were uncorrupted when read back out.

https://github.com/confluentinc/schema-registry/pull/2122 fixed this issue and 6.2.3 now writes good schemas. However this change is breaking for existing schemas.

Attempts to create a schema using 6.2.2 after the 6.2.3 schema has been written, results in a 409 conflict when compatibility checking is on. I haven't tested but I imagine if FULL_TRANSITIVE is enabled, 6.2.3 schemas wouldn't be able to be written at all in cases where ranges of reserved fields could overlap due to the resolved bug.

[dr3s]

https://github.com/confluentinc/schema-registry/issues/2120