Add display name generator to ensure Kraft is used in integration tests

[rayokota]

What

Add display name generator to ensure Kraft is used in integration tests, since the underlying QuorumTestHarness keys off of the display name.

Checklist

• Contains customer facing changes? Including API/behavior changes
• Is this change gated behind feature flag(s)?
  • List the LD flags needed to be set to enable this change
• Did you add sufficient unit test and/or integration test coverage for this PR?
  • If not, please explain why it is not required
• Does this change require modifying existing system tests or adding new system tests?
  • If so, include tracking information for the system test changes

References

JIRA:

Test & Review

Open questions / Follow-ups

[confluent-cla-assistant]

🎉 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.}

[sonarqube-confluent]

Analysis Details

0 Issues

• 0 Bugs
• 0 Vulnerabilities
• 0 Code Smells

Coverage and Duplications

• No coverage information (72.90% Estimated after merge)
• No duplication information (2.10% Estimated after merge)

Project ID: schema-registry

View in SonarQube