Skip more performance tests on Windows ARM

The new pattern `speed` matches the `find_speed` test, and may
match some future performance tests as well.

This is not needed to make tests pass, as `find_speed` was already
passing. However, the `test-fixtures-windows` ARM job takes a very
long time, and this seems that it may be contributing. (It was also
an oversight not to skip it when skipping other performance tests.)

However, the pattern `fuzzed_timeout` is intentionally kept, rather
than being broadened into the pattern `timeout`, since the latter
would match several tests that seem always to complete very fast,
and that test important functionality. (Even `fuzzed_timeout`
itself *usually* completes in less than a tenth of a second.)

Author: EliahKagan

.github/workflows/ci.yml

@@ -215,7 +215,7 @@ jobs:
         include:
           - nextest-extra-args: ''
           - os: windows-11-arm
-            nextest-extra-args: '-- --skip fuzzed_timeout --skip performance'
+            nextest-extra-args: '-- --skip fuzzed_timeout --skip performance --skip speed'
 
     runs-on: ${{ matrix.os }}
 
@@ -258,7 +258,7 @@ jobs:
         include:
           - nextest-extra-args: ''
           - os: windows-11-arm
-            nextest-extra-args: '-- --skip fuzzed-timeout --skip performance'
+            nextest-extra-args: '-- --skip fuzzed-timeout --skip performance --skip speed'
 
     runs-on: ${{ matrix.os }}