Avro and Confluent Schema Registry dependencies are out of date, causing runtime exceptions after upgrades

Summary

The Confluent Schema Registry dependencies are still at 5.2.2, but version 7.1.1 is already available. Class/Method not found, or invalid type exceptions can occur when using the Axual Client in a project where there is a dependency on these new Schema Registry clients.

Steps to reproduce

1. Add the Confluent Schema Registry client 7.1.1 explicitly in a project, next to the Axual (Proxy) client.
2. Use the Axual Avro Serializer/Deserializer
3. While running exceptions occur about type mismatches

Example Project

Not available

What is the current bug behavior?

Type mismatches because we use a Base object that has been replaced.

What is the expected correct behavior?

Working Avro Producers/Consumers

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)

Possible fixes

A Merge request !67 (merged) has been created to fix this