kp should change the generics usage from core API

[cyberhck]

this way, kp consumer can in theory be used without a schema registry or strongly typed definitions.

But we'll add another middleware that takes generics and accepts multiple handler patterns so that we can attach multiple "handlers" depending on what type of message we're getting. This way we keep strongly typed option available.

[cyberhck]

maybe KP keeps some level of generics, it can't really say any or *Kafka.Message with #42 planned, maybe it'll be generics, but not for final processing, rather if it's for kafka.Message or SNS.Message etc.

[github-actions]

🎉 This issue has been resolved in version 1.9.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀