chore: clarify white_flag_flow_enabled values in check_system_overload calls

Signed-off-by: Roman Overko <roman.overko@iota.org>

Author: roman1e2f5p8s

crates/iota-core/src/authority_server/validator.rs

@@ -104,7 +104,8 @@ impl ValidatorService {
             &consensus_adapter,
             transaction.data(),
             state.check_system_overload_at_signing(),
-            false, // white_flag_flow_enabled
+            // `false` means white-flag flow is disabled - ensured by `fp_ensure!` above
+            false,
         );
         if let Err(error) = overload_check_res {
             metrics
@@ -242,7 +243,8 @@ impl ValidatorService {
                 &self.consensus_adapter,
                 certificate.data(),
                 self.state.check_system_overload_at_execution(),
-                false, // white_flag_flow_enabled
+                // `false` means white-flag flow is disabled - ensured by `fp_ensure!` in callers
+                false,
             );
             if let Err(error) = overload_check_res {
                 self.metrics

crates/iota-core/src/authority_server/validator_v2.rs

@@ -161,7 +161,8 @@ impl ValidatorService {
             consensus_adapter,
             transaction.data(),
             state.check_system_overload_at_signing(),
-            true, // white_flag_flow_enabled
+            // `true` means white-flag flow is enabled - ensured by `fp_ensure!` in the caller
+            true,
         ) {
             metrics
                 .num_rejected_tx_during_overload