add run_with_libfunc_profile + AotWithProgram pairing

[avi-starkware]

Summary

Exposes the libfunc-profiling primitives that downstream consumers (e.g. the blockifier in starkware-libs/sequencer) currently maintain locally. The profile-collection pattern is callback-driven so the per-call key (tx hash, etc.) stays out of cairo-native.

Follows the no-enum design from #1612: there is no ContractExecutor dispatch enum; consumers pick an executor type per feature-flag build. Each step is its own commit so it can be reverted independently.

Changes

• metadata::profiler::Profile is now pub (was a private type alias).
• AotContractExecutor::run_with_libfunc_profile<H, F> (gated on with-libfunc-profiling, in new file src/executor/libfunc_profile.rs) wraps run: allocates a unique trace ID, points the executor's cairo_native__profiler__profile_id symbol at it, drains the resulting Profile after run returns, and hands it to a caller-supplied FnOnce(Profile) on success. A ProfilerGuard restores the previous trace ID and drops the LIBFUNC_PROFILE slot on both the success and unwind paths; a process-wide lock plus a thread-local depth counter make concurrent and nested (contract-calls-contract) profiled runs safe.
• AotWithProgram { executor, program }: pairs an AOT executor with the Sierra program it was compiled from (needed to resolve libfunc samples). Exposes inherent methods:
  • run(...) — mirrors AotContractExecutor::run; routes through the profiling bookkeeping (the instrumented .so needs a live profile slot) and discards the profile.
  • run_with_profile(..., FnOnce(Profile, ArcProgram)) — hands the captured profile and the paired program to the callback.
• pub type ArcProgram = Arc<Program> re-export so consumers can name the program handle without a direct cairo-lang-sierra dependency.

Commits (revert points)

1. add run_with_libfunc_profile + AotWithProgram pairing — the profiling primitive.
2. give AotWithProgram inherent run/run_with_profile methods — replaces the former enum dispatch; reverting this commit removes the interchangeable-call-site methods only.

Stack

1. align sierra-emu StarknetSyscallHandler trait/types with cairo-native #1610 — trait alignment
2. extract shared cairo-native-syscalls crate #1611 — extract shared crate
3. add EmuContractExecutor (sierra-emu backend, interchangeable with AotContractExecutor) #1612 — EmuContractExecutor
4. this PR — run_with_libfunc_profile + AotWithProgram

Test plan

• cargo check (default features) clean
• cargo check --features with-libfunc-profiling clean
• cargo check --features sierra-emu,with-libfunc-profiling clean
• cargo check --workspace --all-features clean
• CI green

---

This change is 

[github-actions]

✅ Code is now correctly formatted.

[orizi]

@orizi reviewed 3 files and all commit messages.
Reviewable status: 3 of 4 files reviewed, all discussions resolved (waiting on TomerStarkware and Yoni-Starkware).

[orizi]

@orizi reviewed all commit messages and made 1 comment.
Reviewable status: 1 of 4 files reviewed, 1 unresolved discussion (waiting on avi-starkware, TomerStarkware, and Yoni-Starkware).

---

src/executor.rs line 31 at r3 (raw file):

};
use bumpalo::Bump;
// Re-exported so libfunc-profiling consumers (e.g. blockifier) can refer to the

what kind of reference is expected?
if it is just as a value - since you only use is as Arc<Program> - export:
pub type ArcProgram = std::sync::Arc<cairo_lang_sierra::program::Program>;

[avi-starkware]

@avi-starkware made 1 comment.
Reviewable status: 0 of 5 files reviewed, 1 unresolved discussion (waiting on orizi, TomerStarkware, and Yoni-Starkware).

---

src/executor.rs line 31 at r3 (raw file):

Previously, orizi wrote…

what kind of reference is expected?
if it is just as a value - since you only use is as Arc<Program> - export:
pub type ArcProgram = std::sync::Arc<cairo_lang_sierra::program::Program>;

Done.

[orizi]

@orizi reviewed 5 files and all commit messages, made 1 comment, and resolved 1 discussion.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on avi-starkware, TomerStarkware, and Yoni-Starkware).

---

src/executor/contract_executor.rs line 150 at r5 (raw file):

    /// callers don't have to keep their own copy around just to resolve libfunc samples.
    /// For other variants this is identical to `run` and `on_profile` is never invoked.
    #[cfg(feature = "with-libfunc-profiling")]

following my response to the previous PR - seems to me this is basically the only interesting function.

[avi-starkware]

src/executor/contract_executor.rs line 150 at r5 (raw file):

Previously, orizi wrote…

following my response to the previous PR - seems to me this is basically the only interesting function.

Following my response to your response - removed this file