Split journey tests out into their own CI job

In the `justfile`, this renames the old `ci-test` recipe to
`ci-test-full`, and has `ci-test` no longer clean the target
directory nor run journey tests.

The CI `test` job thus remains the same, but it does moderately
less work. A new CI job, `test-journey`, is introduced to run the
journey tests (still via `ci-test-journey` recipe).

This change is intended to allow greater parallelism, and possibly
make caches work better. The CI `test` job has sometimes been a few
minutes slower than before, ever since 5173e9a (GitoxideLabs#1668). See
comments in GitoxideLabs#1668 for some discussion on this change.

.github/workflows/ci.yml

@@ -75,6 +75,17 @@ jobs:
           GIX_TEST_IGNORE_ARCHIVES: '1'
         run: just ci-test
 
+  test-journey:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+      - uses: dtolnay/rust-toolchain@stable
+      - uses: Swatinem/rust-cache@v2
+      - uses: extractions/setup-just@v2
+      - name: Run journey tests
+        run: just ci-journey-tests
+
   test-fast:
     strategy:
       matrix:
@@ -342,6 +353,7 @@ jobs:
     needs:
       - pure-rust-build
       - test
+      - test-journey
       - test-fast
       - test-32bit
       - lint

justfile

@@ -12,10 +12,15 @@ alias nt := nextest
 # run all tests, clippy, including journey tests, try building docs
 test: clippy check doc unit-tests journey-tests-pure journey-tests-small journey-tests-async journey-tests
 
-# run all tests, without clippy, including journey tests, try building docs (and clear target on CI)
-ci-test: check doc unit-tests clear-target ci-journey-tests
+# run all tests, without clippy, including journey tests, try building docs (and clear target)
+ci-test-full: check doc unit-tests clear-target ci-journey-tests
 
-# run all journey tests, but assure these are running after `cargo clean` (and workaround a just-issue of deduplicating targets)
+# run all tests, without clippy, and try building docs (without clearing the target)
+ci-test: check doc unit-tests
+
+# run all journey tests
+# these should be run in a fresh clone or after `cargo clean`
+# (and workaround a just-issue of deduplicating targets)
 ci-journey-tests: journey-tests-pure journey-tests-small journey-tests-async journey-tests
 
 clear-target: