KIP-345: support static membership

[aiquestion]

Hi this is the impl for kip-345 static membership, pls help to take a look.

• update joingroup/syncgroup/heartbeat/commitoffset request
• donot leavegroup if staticmembership is enabled
• with ut&functional test
• added logic for KIP-394 if static membership is enabled. because we update the joingroup.

[dnwe]

many thanks for this contribution @aiquestion — if you are happy to go ahead and sign the Shopify CLA here then I can proceed to review the changes

[aiquestion]

@dnwe thanks~ i think i signed the CLA before. and when i tried to sign it again, got an error "GitHub username has already signed a CLA"

[dnwe]

@aiquestion ah it looks like probot is confused because your first commit is under a gmail.com e-mail address that maps to your public GitHub username, but the second and third commit have been done under your company e-mail address and that isn't registered to your public GitHub account. That explains why the cla-required label was added then removed and then added back again.

Please can you git rebase origin/main --exec 'git commit --amend --author="Author Name <email@address.com>" --no-edit' (or equivalent in your UI tool of choice) to rebase on main and reset the author to a single consistent one?

[aiquestion]

fixed it. And also revert the gomod change to avoid conflict. thanks

[dnwe]

@aiquestion thank you, this is a really great first contribution to Sarama. Good test coverage and easy to read and understand the code changes. Thanks for your hard work!