Name the segment-size setter parameter for its unit

storeAndForwardMaxSegmentBytes still took a parameter called maxBytes,
which reads as the total cap and reintroduces exactly the ambiguity
the sf_max_segment_bytes rename removes. Every sibling names its
parameter after the method tail: storeAndForwardMaxTotalBytes takes
maxTotalBytes, storeAndForwardDir takes dir, storeAndForwardDurability
takes durability, storeAndForwardSyncIntervalMillis takes millis.

The parameter is now maxSegmentBytes. Signature, the positivity guard,
the exception text argument, and the field assignment all follow. No
behavior changes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: mtopolnik

core/src/main/java/io/questdb/client/Sender.java

@@ -2775,14 +2775,14 @@ public LineSenderBuilder storeAndForwardDurability(SfDurability durability) {
          * (4 MiB). Smaller segments mean faster trim of acked data; larger
          * segments mean fewer rotations.
          */
-        public LineSenderBuilder storeAndForwardMaxSegmentBytes(long maxBytes) {
+        public LineSenderBuilder storeAndForwardMaxSegmentBytes(long maxSegmentBytes) {
             if (protocol != PARAMETER_NOT_SET_EXPLICITLY && protocol != PROTOCOL_WEBSOCKET) {
                 throw new LineSenderException("store_and_forward is only supported for WebSocket transport");
             }
-            if (maxBytes <= 0) {
-                throw new LineSenderException("sf_max_segment_bytes must be positive: ").put(maxBytes);
+            if (maxSegmentBytes <= 0) {
+                throw new LineSenderException("sf_max_segment_bytes must be positive: ").put(maxSegmentBytes);
             }
-            this.sfMaxSegmentBytes = maxBytes;
+            this.sfMaxSegmentBytes = maxSegmentBytes;
             return this;
         }