Investigate removing `AceReplay` from `TraceGenerationContext`

We should look into having the core trace fragment generators generate the `CircuitEvaluation` struct to pass to the `AceChiplet`, instead of having the fast processor include it in `TraceGenerationContext`. The main tradeoffs are size of `TraceGenerationContext` vs speed of `build_trace()` (i.e. what is the performance cost of generating the `AceChiplet` after the core trace, rather than in parallel? Compared to the size increase of `TraceGenerationContext` due to the inclusion of of `CircuitEvaluation`s?)

Context: https://github.com/0xMiden/miden-vm/pull/2188#discussion_r2399162111

Look at the `TraceGenerationContext` and `AceChiplet` in the codebase, likely in the processor or trace generation modules. Understand how `CircuitEvaluation` is currently generated and passed. Profile the performance of `build_trace()` with the current approach versus generating `CircuitEvaluation` after the core trace. The goal is to evaluate the trade-off between context size and generation speed.

由索引模型根據 Issue 內容生成。