DGS-21546 Follow up PR to handle old CP versions (#3902)

[rayokota]

What

Checklist

Please answer the questions with Y, N or N/A if not applicable.

• [ ] Contains customer facing changes? Including API/behavior changes
• [ ] Is this change gated behind config(s)?
  • List the config(s) 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
• [ ] Must this be released together with other change(s), either in this repo or another one?
  • If so, please include the link(s) to the changes that must be released together

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]

• 75.70% Coverage on New Code (is less than 80.00%)

Analysis Details

37 Issues

• 0 Bugs
• 0 Vulnerabilities
• 37 Code Smells

Coverage and Duplications

• 75.70% Coverage (71.40% Estimated after merge)
• No duplication information (2.00% Estimated after merge)

Project ID: schema-registry

View in SonarQube