fix(processor): avoid range check lookup allocations

[giwaov]

Describe your changes

Replaces the per-cycle range check lookup vectors with fixed-capacity storage. Each cycle now tracks up to six lookup values inline, covering the two memory lookups and four stack lookups without allocating in the trace generation hot path.

Closes #2793.

Checklist before requesting a review

• Repo forked and branch created from main.
• Commit messages and codestyle follow conventions.
• Commits are signed.
• Relevant issues are linked in the PR description.
• Tests added for new functionality.
• Documentation/comments updated according to changes.
• Updated CHANGELOG.md.

Tests

• cargo test -p miden-processor range --features testing
• rustfmt --check processor/src/trace/range/mod.rs processor/src/trace/range/aux_trace.rs processor/src/trace/range/tests.rs
• git diff --check

[github-actions]

Automated check (CONTRIBUTING.md)

Findings:

• Add a short Rationale explaining why the change is needed.

Recommendations:

• Consider adding a Test plan or clear review steps.

Next steps:

• Ensure issue Optimize range check lookups with struct-based storage #2793 is assigned to you.
• See CONTRIBUTING.md for expectations.
• If this is a false positive, comment: /quality-review.

[Nashtare]

Superseded by #3119