Bump getdeps Linux CI timeout to 120 minutes for 4-core runner

Summary:
D109390010 switched the openr `getdeps_linux.yml` GitHub Actions workflow from the (non-existent) `8-core-ubuntu-24.04` runner to the available `4-core-ubuntu-24.04` pool by changing `--cpu-cores 8` to `--cpu-cores 4`. Halving the core count roughly doubles build wall-clock, but the workflow's `timeout-minutes` was left at the default `60`, so the 4-core build can now time out before it finishes.

The `timeout-minutes` value is not a CLI flag and is unrelated to `--cpu-cores`. It is read by the getdeps workflow generator from the manifest's `[github.actions] timeout_minutes` key (`workflow_generator.py`), falling back to a hardcoded `60` when unset. openr's manifest had no `[github.actions]` section, so it inherited the `60` default.

This adds `[github.actions] timeout_minutes = 120` to the openr getdeps manifest and regenerates `getdeps_linux.yml` via the same generator invocation used by `update-all-github-actions.sh`, bumping `timeout-minutes: 60` to `120`. The `runs-on: 4-core-ubuntu-24.04` label is unchanged.

Differential Revision: D109903208

fbshipit-source-id: c1a8fd3be939766afdaf0b3d67f468808955a307

Author: Shitanshu Shah

build/fbcode_builder/getdeps/test/fixtures/expected/openr/getdeps_linux.yml

@@ -16,7 +16,7 @@ permissions:
 jobs:
   build:
     runs-on: 8-core-ubuntu-24.04
-    timeout-minutes: 60
+    timeout-minutes: 120
     env:
       SCCACHE_GHA_ENABLED: "on"
     steps:

build/fbcode_builder/manifests/openr

@@ -16,6 +16,10 @@ job_weight_mib = 3072
 # boost.fiber is required and that is not available on macos.
 builder = nop
 
+[github.actions]
+# openr uses a 4-core runner, so allow extra build time.
+timeout_minutes = 120
+
 [dependencies]
 boost
 fb303