MINOR: Add assertions to validate parsed schema cache keys

[rayokota]

What

Add assertions to validate parsed schema cache keys

Checklist

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

• [N] Contains customer facing changes? Including API/behavior changes
• [N/A] Is this change gated behind config(s)?
  • List the config(s) needed to be set to enable this change
• [N/A] Did you add sufficient unit test and/or integration test coverage for this PR?
  • If not, please explain why it is not required
• [N/A] Does this change require modifying existing system tests or adding new system tests?
  • If so, include tracking information for the system test changes
• [N/A] 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.}

[Copilot]

Pull Request Overview

This PR adds assertion statements to validate that schema cache keys are properly formatted before being used in cache operations. The assertions ensure that schema objects used as cache keys have null version and ID fields, which is a requirement for proper cache key generation.

• Added assertions to validate schema parameters in loadSchema, invalidateFromNewSchemaCache, and invalidateFromOldSchemaCache methods
• Ensures schema cache keys are properly formatted with null version and ID fields
• Prevents potential cache corruption or incorrect behavior due to improperly formatted schema keys

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[sonarqube-confluent]

Analysis Details

1 Issue

• 0 Bugs
• 0 Vulnerabilities
• 1 Code Smell

Coverage and Duplications

• 57.10% Coverage (71.50% Estimated after merge)
• No duplication information (2.00% Estimated after merge)

Project ID: schema-registry

View in SonarQube