run miri with a windows target too

it's allocator is quite different, so let's test that

Author: folkertdev

.github/workflows/checks.yaml

@@ -397,22 +397,28 @@ jobs:
   miri:
     name: "Miri"
     runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        include:
+          - target: x86_64-unknown-linux-gnu
+          - target: x86_64-pc-windows-gnu
     steps:
       - uses: actions/checkout@v3
       - name: Install Miri
         run: |
+          rustup target add ${{ matrix.target }}
           rustup toolchain install nightly --component miri
           cargo +nightly miri setup
       - name: Install cargo-nextest
         uses: taiki-e/install-action@56ab7930c591507f833cbaed864d201386d518a8
         with:
           tool: cargo-nextest
       - name: Test public C api with NULL arguments
-        run: "cargo +nightly miri nextest run -j4 -p test-libz-rs-sys null::"
+        run: "cargo +nightly miri nextest run -j4 -p test-libz-rs-sys --target ${{ matrix.target }} null::"
         env:
           RUSTFLAGS: "-Ctarget-feature=+avx2"
       - name: Test allocator with miri
-        run: "cargo +nightly miri nextest run -j4 -p zlib-rs allocate::"
+        run: "cargo +nightly miri nextest run -j4 -p zlib-rs --target ${{ matrix.target }} allocate::"
 
   run-flate2-test-suite:
     name: run flate2 test suite