chore(perf): use constant for address space in tracing_read when possible

[jonathanpwang]

I went through the uses of tracing_read and switched to using constants for better compilation optimization whenever possible, where the requirements on the address space were determined according to ISA.md

I don't think there was really a performance diff: https://github.com/axiom-crypto/openvm-reth-benchmark/actions/runs/16513213487

[codspeed-hq]

CodSpeed WallTime Performance Report

Merging #1899 will not alter performance

_{Comparing INT-4037 (919ea91) with feat/new-execution (a35aa57)}

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

Summary

✅ 24 untouched benchmarks

[shuklaayush]

lgtm

[github-actions]

group	app.proof_time_ms	app.cycles	app.cells_used	leaf.proof_time_ms	leaf.cycles	leaf.cells_used
verify_fibair	(-59 [-5.5%]) 1,018	322,700	17,672,408	-	-	-
fibonacci	(+7 [+0.3%]) 2,223	3,000,556	51,508,517	-	-	-
regex	(-23 [-0.3%]) 7,533	8,330,866	165,431,684	-	-	-
ecrecover	(-4 [-0.4%]) 1,118	274,568	8,596,011	-	-	-
pairing	(+94 [+2.6%]) 3,729	3,725,930	93,105,233	-	-	-

Commit: 919ea91

Benchmark Workflow