starknet_transaction_prover,blockifier_reexecution: drop starknet-sierra-compile sidecar from docker images

[avi-starkware]

Why

Follow-up to #14406, which made blockifier_reexecution compile Sierra→Casm in-process. Both Docker images that build on it shipped the starknet-sierra-compile sidecar binary purely for that path; it is now dead weight.

What

• crates/starknet_transaction_prover/Dockerfile: the prover is built --features stwo_proving (cairo_native disabled), so Sierra→Casm was its only compiler dependency. Removed the install_compiler_binaries.sh --sierra step, the CARGO_TOOLS_ROOT env, and the COPY of the tools tree. The runtime image is now a single self-contained binary — no compiler sidecar at all.
• crates/blockifier_reexecution/replay/Dockerfile: built --features cairo_native, so it still needs starknet-native-compile (the compare-native path, unaffected by blockifier_reexecution: compile Sierra to Casm in-process via library call #14406). Switched the install from both compilers to --native only; kept the tools COPY and the binutils/libc6-dev runtime deps that starknet-native-compile requires. Comments updated accordingly.

Validation

• docker build --check on both Dockerfiles — "Check complete, no warnings found."
• scripts/install_compiler_binaries.sh --native is a supported standalone invocation; the replay base stage installs LLVM 19, so its llvm-config-19 gate passes.
• The prover's zero-compiler runtime was already demonstrated under blockifier_reexecution: compile Sierra to Casm in-process via library call #14406 (the bare binary starts and serves with no compiler binary present anywhere).
• Both images are built by CI on the PR (starknet_transaction_prover_ci.yml docker-build; blockifier_reexecution_docker_publish.yml), giving a full end-to-end build.

Stacked on #14406.

🤖 Generated with Claude Code

[reviewable-StarkWare]

This change is 

[avi-starkware]

• starknet_transaction_prover,blockifier_reexecution: drop starknet-sierra-compile sidecar from docker images #14418 👈 (View in Graphite)
• blockifier_reexecution: compile Sierra to Casm in-process via library call #14406
• main-v0.14.3

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

[cursor]

PR Summary

Low Risk
Packaging-only Dockerfile edits with no application or auth logic changes; replay still ships the native compiler path it needs.

Overview
Removes the unused starknet-sierra-compile sidecar from two Docker images after Sierra→Casm moved in-process (#14406).

starknet_transaction_prover: Drops install_compiler_binaries.sh --sierra, CARGO_TOOLS_ROOT, and copying the tools tree into the runtime image—the prover image is now just the binary plus resources (no compiler sidecar).

blockifier_reexecution replay: Keeps only starknet-native-compile via install_compiler_binaries.sh --native (still needed for cairo_native); comments now say Sierra→Casm is in-process while native compile stays external.

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