apollo_deployments: introduce jsonnet building blocks for infra config

[nimrod-starkware]

No description provided.

[reviewable-StarkWare]

This change is 

[nimrod-starkware]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• apollo_deployments: check applicative config matches deployed app_configs #14489 : 3 dependent PRs (#14480 , #14505 , #14606 )
• apollo_deployments: assemble and deserialize node config from jsonnet #14487
• apollo_deployments: assemble full node config via build.libsonnet #14486
• apollo_deployments: distributed layout jsonnet test #14485
• apollo_deployments: consolidated layout jsonnet test #14484
• apollo_deployments: test hybrid layout for infra config #14483
• apollo_deployments: introduce hybrid layout for infra config #14482
• apollo_deployments: introduce jsonnet building blocks for infra config #14481 👈 (View in Graphite)
• apollo_deployments: jsonnet applicative config #14479
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cursor]

PR Summary

Low Risk
Additive jsonnet libraries with no runtime or deployment wiring in this diff; risk rises once generated config replaces hand-maintained overlays.

Overview
Adds a new lib/infra/ jsonnet layer so per-service components infra can be generated from layout descriptors instead of hand-edited YAML overlays.

catalog.libsonnet fixes the global split between reactive and active node components. templates.libsonnet centralizes default local/remote server and client settings, retry/idle constants tied to scale policy, and canonical reactive component ports (aligned with existing hybrid overlays). component_block.libsonnet exposes small builders for each execution mode (LocalExecutionWithRemoteEnabled, Remote, Disabled, active Enabled/Disabled, etc.).

derive.libsonnet is the main logic: given a layout (services with runs/uses, DNS, ports, scale, localOnly), it builds the full components map for one service—remote clients point at the home service’s URL/port and inherit that service’s retries/idle; local-only reactives get LocalExecutionWithRemoteDisabled; it asserts a service cannot list the same component in both runs and uses. infraFor wraps that for infra-only renderers expected under services/<layout>.jsonnet.

This PR only introduces the libraries; it does not yet wire them into layouts or replace existing overlay files.

^{Reviewed by Cursor Bugbot for commit b14a07c. Bugbot is set up for automated code reviews on this repo. Configure here.}