ci: Compile sqlite3mc with MSVC in the Windows job

A native debug `cargo build -p libsql --all-features` does compile the
bundled SQLite encryption amalgamation (sqlite3mc), but cc-rs derives MSVC
flags from cargo's profile/target and on windows-2025 those flags let MSVC
silently accept breaks that downstream consumers (libsql-js) hit -- e.g.
the SQLite 3.47.0 `#warning` that fails MSVC with error C1021.

Mirror libsql-js's cargo invocation so the same MSVC flags are used:
`--release --target x86_64-pc-windows-msvc`. Also `cargo clean -p libsql-ffi`
so sqlite3mc is rebuilt from source instead of restored from cache.

Author: penberg

.github/workflows/rust.yml

@@ -244,8 +244,21 @@ jobs:
             ~/.cargo/git/db/
           key: ${{ runner.os }}-cargo-registry-${{ hashFiles('**/Cargo.lock') }}
           restore-keys: ${{ runner.os }}-cargo-registry-
+      # Match libsql-js's cargo invocation so the bundled SQLite encryption
+      # amalgamation (sqlite3mc) is compiled with MSVC under the same flags
+      # that fail downstream:
+      #   - --release + --target x86_64-pc-windows-msvc mirror libsql-js, so
+      #     cc-rs / cmake-rs derive the same MSVC C flags. A native debug build
+      #     produces different flags and MSVC silently accepts breaks in
+      #     sqlite3mc (e.g. the SQLite 3.47.0 `#warning` -> C1021).
+      #   - `cargo clean -p libsql-ffi` forces a fresh rebuild so the
+      #     amalgamation actually goes through MSVC, regardless of cache.
+      - name: Install x86_64-pc-windows-msvc target
+        run: rustup target add x86_64-pc-windows-msvc
       - name: build libsql all features
-        run: cargo build -p libsql --all-features
+        run: |
+          cargo clean -p libsql-ffi
+          cargo build -p libsql --all-features --release --target x86_64-pc-windows-msvc
 
   # test-rust-wasm:
   #   runs-on: ubuntu-latest