Add ErrantRecordReporter support

[CodeLikeAGecko]

Add errors.tolerance and ErrantRecordReporter support.
Updating to support kafkaVersion 2.6 which is when
ErrantRecordReporter became available in Kafka connect. Can
also add the following parameters to the http-sink properties
file to handle messages that are reported to the
ErrantRecordReporter.
errors.deadletterqueue.topic.name
errors.deadletterqueue.context.headers.enable
errors.deadletterqueue.topic.replication.factor

Preserving backwards compatibility on batch send by only using
ErrantRecordReporting if non-batch.

[ivanyu]

Related to #34

[AnatolyPopov]

Hi @CodeLikeAGecko, thanks for your contribution.
Could you rebase the branch on top of the current main? We just enabled integration test in GitHub actions and seems they are failing with your changes. And could you add some more integration tests with dead letter queue covering your changes?

[CodeLikeAGecko]

@AnatolyPopov Can you point me to some documentation on how to set up the integration test environment? I am not finding anything, but may have missed it. My environment is that I develop on a remote linux vm. If no documentation, some basic instructions or an example elsewhere on the Internet would be very helpful to me. Thanks!

[AnatolyPopov]

@CodeLikeAGecko Sure! The only thing you need is Docker. If you have Docker installed then ./gradlew integrationTest should run the tests(unless you have any custom Docker configuration). Basically, integration tests are implemented using Testcontainers library. You can use test from src/main/integrationTest as examples.

[CodeLikeAGecko]

@AnatolyPopov Sorry for the long delay. It took me a while to figure things out and my regular job was keeping me busy. But it is hopefully ready now!

[AnatolyPopov]

Sorry for the delay. Here are some comments.

[AnatolyPopov]

Some more comments for things that I missed before.

[CodeLikeAGecko]

@AnatolyPopov Thanks for finding/pointing out these issues. As you will see in the commit message I had some difficulty with a dependency issue that turned out to have been introduced in Confluent Platform v6.0.3. It isn't an area I am very knowledgeable in but it looks like Confluent 6.0.3 started using the jersey-common v2.34 jar file for something. The rest of the test ecosystem was using Jersey 2.31 jar files that was brought in by Kafka version 2.6.3. I think the Confluent-built jar was resolved for a call by the Kafka-related stuff and a method signature had changed, leading to a java.lang.NoSuchMethodError failure in the integration tests. Back in March I couldn't figure it out other than going to the latest Kafka 2.X. This time I was more knowledgeable and isolated it to the Confluent Platform version 6.0.3 allowing Kafka 2.6 to be used.

[AnatolyPopov]

I looked into this dependency-related thing a bit more precisely today so a couple more comments. Hopefully the last thing. Thanks for your patience.

[jlprat]

Until we clarify if the license is compatible, I'll like to hold this PR

[AnatolyPopov]

LGTM. Thanks for your contribution!

Comments addressed