[ANSIENG-3838] | use python3 in kafka_connectors.py (#19)

[mansi-jain-1206]

Description

This PR adds the capability to run connector module with python 3 instead of python 2

Fixes # (issue)

Type of change

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] 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?

Semaphore Job Link

Checklist:

• [ ] 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

[rrbadiani]

I think we should test this for all the scenarios which sets up connectors. This would include scenarios like archive-plain-rhel-fips, broker-scale-up, connect-scale-up, kerberos-rhel, ksql-scale-up, multi-ksql-connect-rhel etc

[mansi-jain-1206]

I think we should test this for all the scenarios which sets up connectors. This would include scenarios like archive-plain-rhel-fips, broker-scale-up, connect-scale-up, kerberos-rhel, ksql-scale-up, multi-ksql-connect-rhel etc

The pipeline link has all tests triggered.

[rrbadiani]

I think we should test this for all the scenarios which sets up connectors. This would include scenarios like archive-plain-rhel-fips, broker-scale-up, connect-scale-up, kerberos-rhel, ksql-scale-up, multi-ksql-connect-rhel etc

The pipeline link has all tests triggered.

The link was pointing to the retry failed scenarios section there I saw only 4 of the tests. On checking the complete run I found that all the tests were ran 😅.