Exclude wall-clock-race LIFO tests from CI

VerifyLifoOrder, RejectWhenBacklogSizeReached and AdaptWhenLimitIncreases
assert strict ordering or sub-100ms latency, which is unreliable on shared
CI runners. Tag them Category=Timing and skip that category in CI/publish;
they still run locally.

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

Author: Karl Solgård

.github/workflows/ci.yml

@@ -23,4 +23,4 @@ jobs:
         run: dotnet build --configuration Release --no-restore
 
       - name: Test
-        run: dotnet test --configuration Release --no-build --verbosity normal
+        run: dotnet test --configuration Release --no-build --verbosity normal --filter "Category!=Timing"

.github/workflows/publish.yml

@@ -22,7 +22,7 @@ jobs:
         run: echo "version=${GITHUB_REF_NAME#v}" >> "$GITHUB_OUTPUT"
 
       - name: Test
-        run: dotnet test --configuration Release
+        run: dotnet test --configuration Release --filter "Category!=Timing"
 
       - name: Pack
         run: dotnet pack --configuration Release -o artifacts -p:Version=${{ steps.ver.outputs.version }}

tests/ConcurrencyLimits.Tests/LifoBlockingLimiterTest.cs

@@ -56,6 +56,7 @@ public void UnblockWhenFullBeforeTimeout()
     }
 
     [Fact]
+    [Trait("Category", "Timing")]
     public void RejectWhenBacklogSizeReached()
     {
         AcquireNAsync(_blockingLimiter, 14);
@@ -70,6 +71,7 @@ public void RejectWhenBacklogSizeReached()
     }
 
     [Fact]
+    [Trait("Category", "Timing")]
     public void AdaptWhenLimitIncreases()
     {
         AcquireN(_blockingLimiter, 4);
@@ -100,6 +102,7 @@ public void AdaptWhenLimitDecreases()
     }
 
     [Fact]
+    [Trait("Category", "Timing")]
     public void VerifyLifoOrder()
     {
         var firstBatch = AcquireN(_blockingLimiter, 4);