Migrate current dispatcher to use ReactiveKafkaConsumer instead of Vertx KafkaConsumer.

[debasishbsws]

progress #2928
The new dispatcher-vertx module is the one that uses Vertx implementation.

Proposed Changes

• Remove all the Vertx Kafka client dependencies from the base dispatcher module.
• Change the current main() to start(..) and call from the other module with specialised Consumer implementation as args.
• migrate all the tests from Direct KafkaConsumer to use ReactiveKafkaConsumer Interface.

Aditional Info

• The implementation of passing handler function to ConsumerRebalanceListener has gotten complex. I will simplify that further in the future.
• Tests for the dispatcher-vertx module are not there as vertx implementations are already well tested.

[knative-prow]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[codecov]

Codecov Report

Merging #3177 (ebff383) into main (fb89db6) will decrease coverage by 0.04%.
The diff coverage is 84.37%.

@@             Coverage Diff              @@
##               main    #3177      +/-   ##
============================================
- Coverage     63.44%   63.41%   -0.04%     
+ Complexity      757      753       -4     
============================================
  Files           167      167              
  Lines         11756    11791      +35     
  Branches        239      238       -1     
============================================
+ Hits           7459     7477      +18     
- Misses         3736     3753      +17     
  Partials        561      561              

Flag	Coverage Δ
java-unittests	79.82% <84.37%> (-0.34%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...enting/kafka/broker/core/OrderedAsyncExecutor.java	58.92% <0.00%> (ø)
...ker/dispatcher/impl/consumer/ConsumerVerticle.java	87.09% <ø> (-6.46%)	⬇️
...broker/dispatcher/impl/consumer/OffsetManager.java	95.78% <ø> (ø)
...oker/dispatcher/main/ConsumerDeployerVerticle.java	67.79% <ø> (ø)
...ve/eventing/kafka/broker/dispatcher/main/Main.java	0.00% <0.00%> (ø)
...patcher/impl/consumer/OrderedConsumerVerticle.java	65.38% <60.00%> (+0.33%)	⬆️
...roker/dispatcher/main/ConsumerVerticleBuilder.java	66.33% <82.60%> (-2.74%)	⬇️
...a/broker/dispatcher/impl/RecordDispatcherImpl.java	89.77% <93.75%> (-0.05%)	⬇️
.../broker/dispatcher/impl/ConsumerRecordContext.java	100.00% <100.00%> (ø)
.../dispatcher/impl/RecordDispatcherMutatorChain.java	100.00% <100.00%> (ø)
... and 3 more

... and 4 files with indirect coverage changes

[debasishbsws]

@pierDipi In the last commit basically I create ConsumerRebalanceListener from the PartisionsRevokeHandlers and pass it to ConsumerVirticleContext and then while calling the subscribe() method I am passing that ConsumerRebalanceListener with it. There may by some redundancy now like in future I can change the PartisionsRevokeHandlers in order to reduce the complexity.

[debasishbsws]

Didn't look into the Benchmark module properly just migrate it to use Vertx implementation.

[debasishbsws]

/test all

[debasishbsws]

/retest-required

[debasishbsws]

I am not sure why the profiler test is failing. maybe because of codegen for now.

[debasishbsws]

Tests are saying to run update-codegen.sh, but after running that DataPlaneContract.java's hasReplyUrf() method is being removed.

But we need that method as we call it from
https://github.com/knative-sandbox/eventing-kafka-broker/blob/fb89db60df3fdb7d6ae6721037a081b5d88a60c8/data-plane/dispatcher/src/main/java/dev/knative/eventing/kafka/broker/dispatcher/main/ConsumerVerticleBuilder.java#L204-L206

[pierDipi]

/lgtm
/approve

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: debasishbsws, pierDipi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [pierDipi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment