deployment: add startup probe to hybrid environment overlays

[nimrod-starkware]

Cross-repo PR: https://github.com/starkware-industries/sequencer-devops/pull/713

Cross-repo PR: https://github.com/starkware-industries/sequencer-devops/pull/713

[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

• deployment: define common env #14196
• deployment: add gcp pod monitoring to hybrid environment overlays #14192
• deployment: add liveness probe to hybrid environment overlays #14191
• deployment: add readiness probe to hybrid environment overlays #14190
• deployment: add startup probe to hybrid environment overlays #14188 👈 (View in Graphite)
• deployment: add monitoring endpoint port to hybrid environment overlays #14187
• deployment: add service ports to hybrid environment overlays #14185
• deployment: move network and consensus ports to hybrid environment overlays #14183
• deployment: add component ports and urls to hybrid environment overlays #14181
• deployment: add recorder_url to hybrid environment overlays #14180
• deployment: add starknet_url to hybrid environment overlays #14179
• main

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

[cursor]

PR Summary

Low Risk
Deployment-only health-check tuning; no application logic or chain config changes beyond probe timing.

Overview
Enables Kubernetes startup probes on hybrid sequencer deployments for mainnet, sepolia-alpha, and sepolia-integration by overriding the shared common.yaml in each environment.

Each overlay turns on startupProbe against /monitoring/alive (the existing monitoring port 8082), with up to ~150s of startup grace (failureThreshold: 30, periodSeconds: 5) before the pod is considered failed to start.

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