fix(ci): skip cache restore when force rebuild is requested

Add 'if: inputs.force != true' condition to cache restore steps to
ensure --force flag actually rebuilds from scratch instead of using
cached artifacts.

Current behavior (broken):
- Cache restore steps always run
- Cache hits prevent rebuilds
- Force flag only affects build conditions (too late)

Fixed behavior:
- Cache restore skipped when inputs.force = true
- Builds run from scratch
- No cache hits to prevent rebuild

Changes:
- build-sea.yml: Skip SEA binary cache restore on force
- build-smol.yml: Skip build/stripped/binary cache restores on force

Note: ccache and WASM caches still restore (desired for speed).

Author: jdalton

.github/workflows/build-sea.yml

@@ -257,6 +257,7 @@ jobs:
           echo "hash=$HASH" >> $GITHUB_OUTPUT
 
       - name: Restore SEA binary cache
+        if: inputs.force != true
         id: sea-cache
         uses: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
         with:

.github/workflows/build-smol.yml

@@ -99,6 +99,7 @@ jobs:
           max-size: 2G
 
       - name: Restore smol build cache
+        if: inputs.force != true
         id: smol-build-cache
         uses: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
         with:
@@ -108,6 +109,7 @@ jobs:
             node-smol-build-${{ matrix.platform }}-${{ matrix.arch }}-
 
       - name: Restore smol stripped binary cache
+        if: inputs.force != true
         id: smol-stripped-cache
         uses: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
         with:
@@ -116,6 +118,7 @@ jobs:
           restore-keys: node-smol-stripped-${{ matrix.platform }}-${{ matrix.arch }}-
 
       - name: Restore smol binary cache
+        if: inputs.force != true
         id: smol-cache
         uses: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
         with: