Fix consumer message latency downsampling

References #129

Author: acogoluegnes

src/main/java/com/rabbitmq/stream/impl/Client.java

@@ -1141,7 +1141,9 @@ public long queryPublisherSequence(String publisherReference, String stream) {
       request.block();
       QueryPublisherSequenceResponse response = request.response.get();
       if (!response.isOk()) {
-        LOGGER.info("Query publisher sequence failed with code {}", formatConstant(response.getResponseCode()));
+        LOGGER.info(
+            "Query publisher sequence failed with code {}",
+            formatConstant(response.getResponseCode()));
       }
       return response.getSequence();
     } catch (RuntimeException e) {

src/main/java/com/rabbitmq/stream/perf/StreamPerfTest.java

@@ -789,7 +789,7 @@ public Integer call() throws Exception {
                                   // become a bottleneck,
                                   // so we downsample and calculate latency for every x message
                                   // this should not affect the metric much
-                                  if (messageCount.incrementAndGet() % 100 == divisor) {
+                                  if (messageCount.incrementAndGet() % divisor == 0) {
                                     try {
                                       long time = Utils.readLong(message.getBodyAsBinary());
                                       // see above why we use current time to measure latency