git-lfs might fail early; let's rely on these caches to be recreated,…

… where possible

Maybe this also means that one should prefer to not use git-lfs at all
and keep data in the packs themselves, it still shouldn't be too much overall.

Butl... for now, let's try to keep it to make the experience.

Here we choose the quick way out by simply checking in the archives in question
and by disabling git-lfs for them.

That way, most of the scripts still run, but we don't have to square the circle
trying to get these scripts portable, or spend a lot of time figuring out why
some baselines don't match perfectly (on windows).

.github/workflows/ci.yml

@@ -79,7 +79,8 @@ jobs:
       - name: "cargo check default features"
         if: startsWith(matrix.os, 'windows')
         run: cargo check --all --bins --examples
-      - run: git lfs fetch && git lfs checkout
+      - run: |
+          git lfs fetch && git lfs checkout || true
       - uses: taiki-e/install-action@v1
         with:
           tool: nextest

gix-glob/tests/fixtures/generated-archives/.gitattributes

@@ -0,0 +1 @@
+make_baseline.tar.xz -filter

gix-object/tests/fixtures/generated-archives/.gitattributes

@@ -0,0 +1 @@
+make_trees.tar.xz -filter

gix-pathspec/tests/fixtures/generated-archives/.gitattributes

@@ -0,0 +1,2 @@
+parse_baseline.tar.xz -filter
+match_baseline_files.tar.xz -filter

gix-submodule/tests/fixtures/generated-archives/.gitattributes

@@ -0,0 +1 @@
+basic.tar.xz -filter

gix/tests/fixtures/generated-archives/.gitattributes

@@ -0,0 +1,2 @@
+make_rev_spec_parse_repos.tar.xz -filter
+make_diff_repo.tar.xz -filter