[KAFKA-19057] Stabilize KIP-932 Kafka protocol RPC definitions in AK 4.1

The early access release of KIP-932 in Apache Kafka 4.0 used unstable APIs because we wanted to retain the flexibility to evolve the design. Of the 12 RPCs in the KIP, ShareGroupHeartbeat, ShareGroupDescribe, ShareFetch and ShareAcknowledge were exposed to consumer applications in AK 4.0. As anticipated, testing has shown that cross-version connections cause problems, in particular because ShareFetch has changed significantly and a 4.1 broker receiving a 4.0 request cannot parse it and throws exceptions.

These RPCs will be stabilised at v1, which will have the effect of preventing 4.0 clients from using share groups with 4.1+ brokers, and preventing 4.1+ clients form using share groups with 4.0 brokers. The remaining RPCs in KIP-932 do not have any such concerns and will be stabilized at v0 in the usual way.