Add a benchmark to verify performance

[mariomastrodicasa]

Is your feature request related to a problem? Please describe.
The project needs a benchmark to verify its performance.

Describe the solution you'd like
Add some benchmark associated to the produce/consume API calls to verify performance and identify possible bottlenecks.

Describe alternatives you've considered
Introduce some counter or other mechanism to measure time like Stopwatch.

Additional context
N/A

[masesdevelopers]

The benchmark cannot be built with an absolute vision. What it can done is to have some function that executes in the same way, but use a different underlying mechanism: i.e. use KNet in some function and use e.g. Confluent.Kafka in other.
Pairing this two executions it is possible to compare both implementations.
Anyway it is mandatory to use configurations which, more or less, create similar environments: if the configuration is in one case, or in another, is optimized the comparison has no real meaning. The previous consideration comes from the number of possible options can be used when a consumer/producer is allocated, how the underlying mechanism manages message batching both in receive mode (consume) and send mode (produce).

[mariomastrodicasa]

Maybe a new option shall be added, or a value shall be calculated, about the Average, stdev and CV without the maximum and minimum values in the series. Max and Min in a series can be affected from spurius conditions and can affect the other measurements: try to remove them and calculate the values.

[mariomastrodicasa]

Try to integrate BenchmarkDotNet (at https://github.com/dotnet/BenchmarkDotNet)