Clarify commit strategy fallback behavior in documentation; update test method signature for consistency

Author: David Garza

src/modules/Elsa.Workflows.Core/CommitStates/Extensions/ModuleExtensions.cs

@@ -23,7 +23,7 @@ public static WorkflowsFeature UseCommitStrategies(this WorkflowsFeature workflo
 
     /// <summary>
     /// Sets the specified workflow commit strategy as the global default for all workflows that do not specify their own strategy.
-    /// The strategy will be automatically registered if not already present.
+    /// The strategy will not be added to the registry and serves only as a fallback.
     /// </summary>
     /// <param name="workflowsFeature">The workflows feature.</param>
     /// <param name="strategy">The workflow commit strategy instance to use as the default.</param>
@@ -36,7 +36,7 @@ public static WorkflowsFeature WithDefaultWorkflowCommitStrategy(this WorkflowsF
 
     /// <summary>
     /// Sets the specified activity commit strategy as the global default for all activities that do not specify their own strategy.
-    /// The strategy will be automatically registered if not already present.
+    /// The strategy will not be added to the registry and serves only as a fallback.
     /// </summary>
     /// <param name="workflowsFeature">The workflows feature.</param>
     /// <param name="strategy">The activity commit strategy instance to use as the default.</param>

test/integration/Elsa.Workflows.IntegrationTests/Scenarios/DefaultWorkflowCommitStrategy/Tests.cs

@@ -116,7 +116,7 @@ public async Task NoCommitsWithoutAnyWorkflowCommitStrategy()
     }
 
     [Fact(DisplayName = "Default workflow strategy is not visible in commit strategy registry")]
-    public async Task DefaultWorkflowStrategyNotInRegistry()
+    public void DefaultWorkflowStrategyNotInRegistry()
     {
         // Arrange
         var services = new TestApplicationBuilder(_testOutputHelper)