fix(ci): reduce Bazel jobs to 1 to isolate OOM crash

The latest adev-staging-deploy.yml run on main failed with a genuine
in-VM OOM signature (truncated log line + exit code 1) mid-compile at
[17,472/17,628], not the runner-shutdown flakiness seen in prior runs.
With --jobs=2, two concurrent Bazel actions (ng_package rollup, tsc
workers) can each exceed the memory estimate --local_resources=memory
schedules against.

Test --jobs=1 in isolation, keeping memory=4096 unchanged, to see if
serializing action execution avoids the OOM before also lowering the
memory budget.

Author: ricardochl

.github/workflows/adev-staging-deploy.yml

@@ -34,7 +34,7 @@ jobs:
             # Limit resources for CI runners (ubuntu-latest: 7GB RAM, 2 CPUs)
             build --local_resources=memory=4096
             build --local_resources=cpu=2
-            build --jobs=2
+            build --jobs=1
             build --discard_analysis_cache
             build --nokeep_state_after_build
 

.github/workflows/ci.yml

@@ -31,9 +31,10 @@ jobs:
             # Limit resources for CI runners (ubuntu-latest: 7GB RAM, 2 CPUs)
             build --local_resources=memory=4096
             build --local_resources=cpu=2
-            build --jobs=2
+            build --jobs=1
             build --discard_analysis_cache
             build --nokeep_state_after_build
+            
             # Allow network access in sandbox for Algolia API calls during SSR prerendering.
             build --sandbox_default_allow_network
       - name: Install Dependencies