Reduce nightly test repetitions from 100 to 5

The nightly schedule runs every test 100x (via pytest --count) across
~60 matrix configurations on 3 platforms, causing 6-12 hour runtimes
that block the runner queue for PR CI during the day. 5 repetitions
still provide useful flaky-test signal without monopolizing runners.

Co-Authored-By: Leo's bot <noreply@github.com>

Author: leofang

.github/workflows/ci.yml

@@ -343,7 +343,7 @@ jobs:
       build-type: pull-request
       host-platform: ${{ matrix.host-platform }}
       build-ctk-ver: ${{ needs.ci-vars.outputs.CUDA_BUILD_VER }}
-      nruns: ${{ (github.event_name == 'schedule' && 100) || 1}}
+      nruns: ${{ (github.event_name == 'schedule' && 5) || 1}}
       skip-bindings-test: ${{ !fromJSON(needs.detect-changes.outputs.test_bindings) }}
 
   # See test-linux-64 for why test jobs are split by platform.
@@ -368,7 +368,7 @@ jobs:
       build-type: pull-request
       host-platform: ${{ matrix.host-platform }}
       build-ctk-ver: ${{ needs.ci-vars.outputs.CUDA_BUILD_VER }}
-      nruns: ${{ (github.event_name == 'schedule' && 100) || 1}}
+      nruns: ${{ (github.event_name == 'schedule' && 5) || 1}}
       skip-bindings-test: ${{ !fromJSON(needs.detect-changes.outputs.test_bindings) }}
 
   # See test-linux-64 for why test jobs are split by platform.
@@ -393,7 +393,7 @@ jobs:
       build-type: pull-request
       host-platform: ${{ matrix.host-platform }}
       build-ctk-ver: ${{ needs.ci-vars.outputs.CUDA_BUILD_VER }}
-      nruns: ${{ (github.event_name == 'schedule' && 100) || 1}}
+      nruns: ${{ (github.event_name == 'schedule' && 5) || 1}}
       skip-bindings-test: ${{ !fromJSON(needs.detect-changes.outputs.test_bindings) }}
 
   doc: