ci: pin action to v3 and remove moon's --concurency usage

v3 was the action version of the previous base job.
We want to do changes one by one, and v4 (current main) does not work
without the concurrency change. This just brings the concurrency change
that we will need to set the action version to the latest (v4) again.

Author: GuillaumeLagrange

.github/workflows/ci.yml

@@ -62,15 +62,15 @@ jobs:
 
       - name: Run benchmarks with tinybench-plugin
         # use version from `main` branch to always test the latest version, in real projects, use a tag, like `@v2`
-        uses: CodSpeedHQ/action@main
+        uses: CodSpeedHQ/action@v3
         with:
           run: pnpm --filter ${{ matrix.example }} bench-tinybench
         env:
           CODSPEED_SKIP_UPLOAD: true
           CODSPEED_DEBUG: true
       - name: Run benchmarks with benchmark.js-plugin
         # use version from `main` branch to always test the latest version, in real projects, use a tag, like `@v2`
-        uses: CodSpeedHQ/action@main
+        uses: CodSpeedHQ/action@v3
         with:
           run: pnpm --filter ${{ matrix.example }} bench-benchmark-js
         env:

.github/workflows/codspeed.yml

@@ -25,7 +25,7 @@ jobs:
 
       - name: Run benchmarks
         # use version from `main` branch to always test the latest version, in real projects, use a tag, like `@v2`
-        uses: CodSpeedHQ/action@main
+        uses: CodSpeedHQ/action@v3
         with:
           run: |
             pnpm moon run --concurrency 1 :bench
@@ -51,7 +51,7 @@ jobs:
 
       - name: Run benchmarks
         # use version from `main` branch to always test the latest version, in real projects, use a tag, like `@v2`
-        uses: CodSpeedHQ/action@main
+        uses: CodSpeedHQ/action@v3
         with:
           # Only tinybench supports walltime for now
           run: |