fix: complete OP pre-bedrock error tracing

[triple-CCC]

Summary

• Squash the writer changes into one commit: cc184dc.
• Pin Pipeline to 67ae274c3d3e041ccece432ddf52c92524983f2d (fix: correct OP pre-bedrock error trace propagation pipeline#172) for ancestor-failure propagation and replay completeness checks.
• Capture early CALL/CALLCODE/DELEGATECALL/STATICCALL/CREATE failures without changing validation order, execution rules, gas or state transitions.
• Fail trace_debankBlock on missing receipts, replay errors or incomplete/inconsistent root traces; preserve canonical state-root verification.
• Keep only .github/workflows/build.yaml, using native 16-core amd64/arm64 runners, AWS OIDC and l2geth/Dockerfile with repository-root context.
• Reuse public.ecr.aws/b2h7a5c4/chaintable/op-geth with isolated prebedrock- tags. Never publish latest or per-chain aliases.
• Remove the newly added writer regression-test file and Dockerfile go test command as requested. Retain the existing geth version startup check. Baseline tests and the pre-existing untracked local l2geth/keccak_test.go are unchanged; Pipeline PR #172 is unchanged.

Verification

• GitHub Actions https://github.com/Chaintable/optimism/actions/runs/38233274787 PASSED for cc184dc: build-amd64, build-arm64 and merge-manifest all succeeded.
• Both architectures compiled and published their images, and passed geth version (1.9.10-stable, Go 1.23.12). The current workflow does not run regression tests.
• Published image: public.ecr.aws/b2h7a5c4/chaintable/op-geth:prebedrock-cc184dc.
• Manifest digest: sha256:6acb31fc7ec8a12ba31b1529b5c6822ddd8e8d4b42f04b2b21b9c36902c9ec54; inspected and confirmed linux/amd64 and linux/arm64.
• Production source and Pipeline dependency are unchanged from the previously tested cc54b22; regression results before test removal remain in run https://github.com/Chaintable/optimism/actions/runs/38219768521.
• Mac: source/static checks and Git only for this revision; no local compilation or tests.

Boundaries

• Error-trace semantics align with Bedrock op-reth; legacy execution rules and the RPC height-based interface remain unchanged.
• Newly captured missing calls can legitimately shift subsequent trace/log positions and derived IDs.
• No PR merge, deployment, node restart or historical S3 writes.