blockifier: rename field to cairo native mode to match type name

[ArniStarkware]

Note

Medium Risk
Mostly a mechanical rename, but it changes serialized config keys and runtime config wiring; misaligned config files or external tooling still using the old key could break native compilation behavior or startup.

Overview
Renames the Cairo Native execution-mode field in CairoNativeRunConfig from cairo_native_run_mode to cairo_native_mode across the blockifier crate (including serialization via SerializeConfig) and all call sites (native/trivial class managers, tests, integration tests, and blockifier_reexecution).

Updates config surface area accordingly by changing the JSON schema key and deployment app configs (batcher/gateway and their replacers) to emit/expect ...cairo_native_run_config.cairo_native_mode instead of ...cairo_native_run_config.cairo_native_run_mode, plus aligns the Python bridge (native_blockifier) conversion to populate the renamed field.

^{Written by Cursor Bugbot for commit 8b19a17. This will update automatically on new commits. Configure here.}

[reviewable-StarkWare]

This change is 

[ArniStarkware]

• blockifier: rename field to cairo native mode to match type name #12868 👈 (View in Graphite)
• main-v0.14.2

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Artifacts upload workflows:

• Started at 2026-02-25T19:03:14Z

[avi-starkware]

@avi-starkware reviewed 16 files and all commit messages, and made 1 comment.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on ArniStarkware).