SchemaRegistrySerde: Avro deserialization via topic name

[1-alex98]

Avro deserialization without magic byte using lookup by topic name as fallback like in serialization Closes #4520

• Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

[github-actions]

Hello there 1-alex98! 👋

Thank you and congrats 🎉 for opening your first PR on this project! ✨ 💖

We will try to review it soon!

[1-alex98]

Sonar is happy -> Where can I view that?

[1-alex98]

The Pipeline failing seems to be unrelated to the PR

[Haarolean]

@1-alex98 hey, this repo is not maintained (#4255). Could you raise the PR at https://github.com/kafbat/kafka-ui instead?

[1-alex98]

Why not write that into the readme or pin an issue that says something like that or archieve the repo? @Haarolean

[Haarolean]

Why not write that into the readme or pin an issue that says something like that or archieve the repo? @Haarolean

you're asking the wrong person. Please feel free to contact provectus and ask why, despite the promises in #4255, none are being held.