chore: Remove send + sync bound on executor

[Schaeff]

It is not required after a small refactor.

[Copilot]

Pull Request Overview

This PR removes the Send + Sync trait bounds from the Executor type in the VmExecutionConfig trait. The change is made possible by refactoring the filtered_execution_frequencies method to use zip_eq and filter_map instead of enumerate and separate indexing, eliminating the need for thread-safety constraints on the executor type.

• Removed Send + Sync bounds from VmExecutionConfig::Executor trait
• Refactored filtered_execution_frequencies method to use iterator combinators instead of indexing
• Simplified the filtering logic using filter_map and then_some

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
crates/vm/src/arch/config.rs	Removed Send + Sync trait bounds from the Executor associated type
crates/vm/src/arch/interpreter_preflight.rs	Refactored method implementation to eliminate need for Send + Sync bounds and improved iterator usage

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[jonathanpwang]

@Schaeff there is some clippy/fmt issue

[jonathanpwang]

The CI errors are something about zip_eq where the imports necessary differ with feature = "parallel" on or off

[jonathanpwang]

@Schaeff please try to fix the CI issues again

[jonathanpwang]

The other two tests are failing for unrelated reasons