KAFKA-18437: Correct version of ShareUpdateRecord value

[AndrewJSchofield]

The versions of coordinator record keys are hijacked to distinguish between the record types. Coordinator record values are always version 0.

The JSON schema definition of ShareUpdateRecord uses version 0, but the version number used when constructing the record was version 1.

This patch applies to AK 4.0 only because this code has been superseded and the error was already been fixed.

Committer Checklist (excluded from commit message)

• Verify design and implementation
• Verify test coverage and CI build status
• Verify documentation (including upgrade notes)

[chia7712]

the ShareUpdateKey file has validVersions=1 in 4.0 but "validVersions=0" in trunk. It is fine as we don't use the version to check serialized field. Also, we won't bump the version for those coordinator-keys. However, it is still a weird thing to have two different validVersions for same record. Maybe we can add some comments to the json file in 4.0?

[AndrewJSchofield]

the ShareUpdateKey file has validVersions=1 in 4.0 but "validVersions=0" in trunk. It is fine as we don't use the version to check serialized field. Also, we won't bump the version for those coordinator-keys. However, it is still a weird thing to have two different validVersions for same record. Maybe we can add some comments to the json file in 4.0?

This is true for all of the key schemas in the group coordinator in 4.0 too, such as ConsumerGroupCurrentMemberAssignmentKey.

[dajac]

lgtm