Clarifies post-SUBACK delay configuration property

Renames the `clusterSyncDelayInMillis` property to `postSubAckDelayForClusterSync`. This improves clarity by explicitly indicating the delay occurs after a successful SUBACK for cluster synchronization. Updates include the configuration interface, its usage, log messages, and documentation.

fixes #65

Author: amitjoy

README.md

@@ -154,7 +154,7 @@ The `in.bytehue.messaging.subscriber` PID can be used to configure the subscribe
 |---|---|---|---|
 | `timeoutInMillis` | Default timeout for synchronously subscribing to the broker (in milliseconds) | Long | `15000` |
 | `qos` | Default QoS for subscriptions unless specified | Integer | `0` |
-| `clusterSyncDelayInMillis` | Cluster Sync Delay - Wait after SUBACK (in milliseconds) | Long | `0` |
+| `postSubAckDelayForClusterSync` | Delay in milliseconds to wait after a successful SUBACK to allow for cluster synchronization | Long | `0` |
 
 #### Publisher Configuration
 

in.bytehue.messaging.mqtt5.provider/src/main/java/in/bytehue/messaging/mqtt5/provider/MessageSubscriptionProvider.java

@@ -114,8 +114,9 @@ public final class MessageSubscriptionProvider implements MessageSubscription {
 		@AttributeDefinition(name = "Default QoS for subscriptions unless specified", min = "0", max = "2")
         int qos() default 0;
 
-		@AttributeDefinition(name = "Cluster Sync Delay", description = "Wait after SUBACK (in milliseconds)", min = "0")
-		long clusterSyncDelayInMillis() default 0L;
+		@AttributeDefinition(name = "Post SUBACK Delay For Cluster Sync", description = "Delay in milliseconds to wait after a successful SUBACK "
+				+ "to allow for cluster synchronization", min = "0")
+		long postSubAckDelayForClusterSync() default 0L;
 	}
 
 	private LogHelper logHelper;
@@ -380,12 +381,12 @@ public SubscriptionAck _subscribe(final MessageContext context) { //NOSONAR
 
             future.get(config.timeoutInMillis(), MILLISECONDS);
 
-            long delay = config.clusterSyncDelayInMillis();
+            long delay = config.postSubAckDelayForClusterSync();
             if (delay > 0) {
-                logHelper.debug("Cluster Sync: Subscription acknowledged. Waiting {}ms for propagation...", delay);
+                logHelper.debug("[Post SUBACK Delay] Subscription acknowledged. Waiting {}ms for cluster synchronization...", delay);
                 // It is safe to sleep here because we are on the caller's thread, not the HiveMQ Network thread.
                 Thread.sleep(delay);
-                logHelper.debug("Cluster Sync: Propagation wait of {}ms finished", delay);
+                logHelper.debug("[Post SUBACK Delay] Wait of {}ms for cluster synchronization finished", delay);
             }
 
             return SubscriptionAck.of(stream, subscription.id);

in.bytehue.messaging.mqtt5.provider/src/test/java/in/bytehue/messaging/mqtt5/provider/MessageSubscriptionEventTest.java

@@ -123,7 +123,7 @@ public int qos() {
 				}
 
 				@Override
-				public long clusterSyncDelayInMillis() {
+				public long postSubAckDelayForClusterSync() {
 					return 0;
 				}