build: temporarily force local spawn strategy during release builds

[josephperrott]

Temporarily force the local spawn strategy for building during release due to seeing unexpected and yet to be traced failures in the Sass compiler within workers.

[devversion]

@josephperrott do you have a link to these errors?

Also, please create a tracking issue for this. We tend to leave such TODOs forever

[josephperrott]

ERROR: /usr/local/google/home/amysorto/components/src/material/datepicker/BUILD.bazel:90:12: SassCompiler src/material/datepicker/date-range-input.css failed: Worker process did not return a WorkResponse:

---8<---8<--- Start of log, file at /usr/local/google/home/amysorto/.cache/bazel/_bazel_amysorto/9aa9d212bc5094d24a51ae5af82e4d63/bazel-workers/worker-40-SassCompiler.log ---8<---8<---
(empty)
---8<---8<--- End of log ---8<---8<---
ERROR: /usr/local/google/home/amysorto/components/src/material/BUILD.bazel:47:11 Bundling types (src/material/datepicker/datepicker_public_index.d.ts) failed: Worker process did not return a WorkResponse:

---8<---8<--- Start of log, file at /usr/local/google/home/amysorto/.cache/bazel/_bazel_amysorto/9aa9d212bc5094d24a51ae5af82e4d63/bazel-workers/worker-40-SassCompiler.log ---8<---8<---
(empty)
---8<---8<--- End of log ---8<---8<---
INFO: Elapsed time: 22.238s, Critical Path: 5.60s
INFO: 106 processes: 49 internal, 3 linux-sandbox, 54 worker.
FAILED: Build did NOT complete successfully

[devversion]

I think it's better, if we do this, to disable worker just for the bundle type action. I think I saw a similar issue for this reported by SBB (some swiss railway company using our Bazel setup).

We should also spend some time investigating, I guess.

[devversion]

Hmm, but it sounds like it's the SassCompiler as well... that's new. Might be some local stdout/stderr issue. I'm good unblocking for now, but we shouldn't leave this forever 😄