fix: Use RunContext to avoid cargo_metadata in production context

[ratankaliani]

• Introduce RunContext to delineate binary paths in the development context vs production (Docker) context.
• Only include the necessary binaries in the Docker image.
• GetSpanBatches -> GetRangeProofBoundaries.

For a more optimized build, we can use a path that is not reliant on the binary being in a cargo workspace. This means that we can keep only the binaries we need and nothing else.

cargo_metadata should not be used in a production context, because it requires bloated builds in order to execute.

In a future PR, we can optimize the Docker build in the second stage. We should verify if some of the dependencies (e.g. SP1, Rust) are necessary, along with the installed Ubuntu libraries.

[github-actions]

Metric	Value
Batch Start	20,822,130
Batch End	20,822,135
Witness Generation (seconds)	117
Execution Duration (seconds)	79
Total Instruction Count	1,800,206,699
Oracle Verify Cycles	411,910,799
Derivation Cycles	837,780,659
Block Execution Cycles	480,162,174
Blob Verification Cycles	168,284,637
Total SP1 Gas	2,118,806,822
Number of Blocks	6
Number of Transactions	57
Ethereum Gas Used	24,700,568
Cycles per Block	300,034,449
Cycles per Transaction	31,582,573
Transactions per Block	9
Gas Used per Block	4,116,761
Gas Used per Transaction	433,343
BN Pair Cycles	0
BN Add Cycles	0
BN Mul Cycles	0
KZG Eval Cycles	0
EC Recover Cycles	1,128,154