* Fix failed drive-kop tests

* Fix format violation

…essaging#376)

* exclude artemis netty transitive dependency

* lint pom.xml

---------

Co-authored-by: sky.kistler <sky.kistler@reddit.com>

* [nats] Add storage type to config

so one can test with file or memory stream.

* [nats] Add maxBytes to config

so one can prevent NATS running out of memory incase the storage type is set to "Memory"

…aging#390)

…nmessaging#392)

…n-plugin:2.25.0:check (check) on project driver-rocketmq: The following files had format violations: [ERROR] src/main/java/io/openmessaging/benchmark/driver/rocketmq/RocketMQBenchmarkDriver.java' (openmessaging#399)

Co-authored-by: nuolin <lushiji@xiaohongshu.com>

* Grow the histogram buffer if it is too small

When we serialize a histogram to a byte array, the intermediate
ByteBuffer that we pass may be too small which may result in silent
truncation of the encoded histogram.

This will manifest on the driver side as a decoding failure.

This change detects this case and grows the buffer by a
factor of 2 until it fits.

Fixes openmessaging#369.

* Add Histogram deserialization test

Add an addition test to the HistogramSerDeTest which tests that
histogram deserialization roundtrips even when the serialized size
exceeds the initial buffer.

* Fixed spotbugs warnings

---------

Co-authored-by: Matteo Merli <mmerli@apache.org>

openmessaging#394)

Bumps [com.rabbitmq:amqp-client](https://github.com/rabbitmq/rabbitmq-java-client) from 4.8.0 to 5.18.0.
- [Release notes](https://github.com/rabbitmq/rabbitmq-java-client/releases)
- [Commits](rabbitmq/rabbitmq-java-client@v4.8.0...v5.18.0)

---
updated-dependencies:
- dependency-name: com.rabbitmq:amqp-client
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…penmessaging#397)

Signed-off-by: Ning Yu <ningyu@automq.com>

Some known issues with current version:
- PEM files cannot be used because of a bug.

…ging#412)

* Support set client.id with Zone ID for Kafka driver

* Apply spotless fix