deployment: wrap cdk8s requirements in docker container

[idan-starkware]

Note

Medium Risk
Build/entrypoint scripts run as root during image build/startup and install multiple external tools, so failures or misconfiguration could impact developer environments and CI if adopted. No runtime application logic changes; the primary risk is in developer tooling and container security posture (sudoers, kubeconfig handling).

Overview
Adds a containerized workflow for deployments/sequencer so contributors can run cdk8s synth without installing Python/Node/pipenv/kubectl locally. This introduces a Docker image build (local/Dockerfile + dependencies.sh) that installs required tooling (including gcloud/kubectx) and a wrapper script local/run-in-docker.sh that builds/runs the container with the repo mounted.

The container entrypoint (docker-entrypoint.sh) creates a user matching host UID/GID, mounts host kubeconfig read-only then copies it to a writable location, enables passwordless sudo, and auto-runs setup.sh to perform pipenv install + cdk8s import when needed. Documentation in deployments/sequencer/README.md is reorganized/expanded to cover both manual and Docker-based setup and provide clearer usage/config references.

^{Written by Cursor Bugbot for commit 11ff01f. This will update automatically on new commits. Configure here.}

[reviewable-StarkWare]

This change is 

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[idan-starkware]

@idan-starkware reviewed 10 files and all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @idan-starkware).