starknet_transaction_prover: add ConfigMap docs and full config reference

[avi-starkware]

Summary

• Add a Kubernetes deployment section to the README with ConfigMap creation, Deployment YAML, and configuration precedence docs
• Add a Full configuration reference section documenting all nested JSON config fields (bouncer_config, storage_proof_config, contract_class_manager_config)
• Expand resources/example-config.json to show the complete config structure with all nested fields
• Remove the --bouncer-config-override CLI arg and BOUNCER_CONFIG_OVERRIDE env var — the JSON config file now covers this use case

Test plan

• cargo check -p starknet_transaction_prover passes
• All 41 unit tests pass (cargo test -p starknet_transaction_prover)
• example-config.json validates as valid JSON
• All serde field names verified against source code

Stacked on #13158 (avi/privacy/external-dev-experience)

🤖 Generated with Claude Code

---

Note

Medium Risk
Mostly documentation/config reference updates, but it removes the --bouncer-config-override/BOUNCER_CONFIG_OVERRIDE path, which could break existing deployments relying on that override mechanism.

Overview
Adds a full JSON configuration reference to the starknet_transaction_prover README (including detailed bouncer_config structure) and new Kubernetes deployment guidance using a ConfigMap, plus explicit configuration precedence rules.

Expands resources/example-config.json to include the complete nested config structure (runner/storage proof, executor/bouncer limits & weights, and contract class manager/native compiler settings). Removes the --bouncer-config-override CLI/env override path in src/server/config.rs and updates tests accordingly, and logs the effective resolved ServiceConfig at startup.

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

[reviewable-StarkWare]

This change is 

[avi-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

• starknet_transaction_prover: add deployment smoke test script #13159
• starknet_transaction_prover: add manual and deployment smoke testing guides #13158
• starknet_transaction_prover: add TLS integration tests #13138
• starknet_transaction_prover: add CORS and config validation tests #13136
• starknet_transaction_prover: add exhaustive error enum and error mapping tests #13135
• starknet_transaction_prover: add committer utils unit tests #13134
• starknet_transaction_prover: add prover input validation unit tests #13133
• starknet_transaction_prover: sanitize error messages returned to clients #13132
• starknet_transaction_prover: add ConfigMap docs and full config reference #13167 👈 (View in Graphite)
• starknet_transaction_prover: add external developer docs #13129
• starknet_transaction_prover: validate request inputs before proving #13125
• main-v0.14.2

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

[cursor]

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

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[cursor]

Startup logging may expose sensitive RPC API keys

Low Severity

The new info!("Effective configuration: {:#?}", service_config) unconditionally logs the entire ServiceConfig at startup, including prover_config.rpc_node_url. RPC URLs commonly embed API keys (e.g. https://mainnet.infura.io/v3/SECRET_KEY). Previously, the URL was only logged when a CLI override changed it; now it's always emitted to the info log level regardless of how it was configured.