⚡ Bolt: Optimize VM instruction fetch by removing redundant array lookup

[Tcode-Motion]

💡 What: Removed a redundant, deep array index lookup in the core VM loop (execute_loop) when fetching instruction operands. It now directly borrows from the existing inst reference.

🎯 Why: The original code fetched the inst reference but then re-fetched the operands via self.module.functions[frame.function_idx as usize].chunk.instructions[ip].operands.as_slice(). This added unnecessary bounds checks and pointer chasing inside the most performance-critical part of the virtual machine (the fetch-decode-execute loop).

📊 Impact: Expected to provide a micro-optimization to overall VM execution time by reducing CPU instructions per cycle in the hot loop.

🔬 Measurement: Run cargo run --release --manifest-path Cargo.toml --bin tsc benchmark or cargo bench -p techscript_vm. Time improvements may be small but the generated IR/assembly will definitively show fewer bounds check branches.

---

PR created automatically by Jules for task 11168865889127833758 started by @Tcode-Motion

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.