Multiple protocols ansieng 2902

[mansi-jain-1206]

Description

This PR adds capability to support multiple authentication on a single listener. 1-pager

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

ZK Kraft Migration

Checklist:

• [x] Any variable/code changes have been validated to be backwards compatible (doesn't break upgrade)
• [x] I have added tests that prove my fix is effective or that my feature works
• [ ] If required, I have ensured the changes can be discovered by cp-ansible discovery codebase
• [x] My code follows the style guidelines of this project
• [x] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] Any dependent changes have been merged and published in downstream modules

[confluent-cla-assistant[bot]]

:tada: All Contributor License Agreements have been signed. Ready to merge.
_{Please push an empty commit if you would like to re-run the checks to verify CLA status for all contributors.}

[mansisinha]

Needs some more testing, added a few open questions like

1. How are we maintaining the preference for client protocol? How are we testing that the correct client properties are getting created for cp components as kafka clients?
2. How have we tested the backwards compatibility?
3. Have we tested any upgrade scenario where customer might upgrade from plain to plain,kerberos? what happens when customer upgrades from plain to kerberos,plain?

[mansi-jain-1206]

1. First protocol takes preference for inter component communication while the customer can create its own client to communicate with the other protocols.
2. Yes have added the semaphore job links in the PR description.
3. Have tested the upgrade scenarios for the following cases:
   • plain to kerberos,plain
   • kerberos,plain to plain

Upgrade needs to steps similar to the ones defined at https://docs.confluent.io/ansible/current/ansible-upgrade.html.

1. Upgrade Zookeeper or Controller
2. Upgrade Kafka Broker
3. Upgrade other components

[mansisinha]

Overall changes look good now, please list down the upgrade scenarios tried for different controller and broker sasl protocol as well

[mansi-jain-1206]

More upgrade scenarios around controller protocol are covered in scram changes PR because this feature was needed to implement that. sasl_protocol: kerberos -> plain -> kerberos,plain -> plain,kerberos