fix(cli): correctly resume existing runs through rerun

[Ayoubbelguellaoui]

What Changed

-chipcompiler/cli/project/run_existing.py: route existing-workspace resume through rerun.run_resume (with preserve_cli_stdio and bounded_resume_r
-test/cli/commands/conftest.py: DummyFlow.create_step_workspaces accepts kwargs
-test/cli/commands/test_flow_continuation.py: added test_stale_suffix_reexecuted_via_run_resume spy test

Scope

Select the areas touched by this PR:

• CLI - command behavior, Typer command surface, output formats, or workspace commands.
• Flow/runtime - workspace lifecycle, EngineFlow, step execution, logs, metrics, or artifacts.
• EDA integration - Yosys, ECC-Tools, DreamPlace, KLayout, PDKs, or native/runtime wrappers.
• Build/package - Nix, PyInstaller, wheels, uv.lock, or release artifacts.
• CI/release - GitHub Actions, version checks, changelog, or release automation.
• Tests/docs only

Runtime And Packaging Impact

• No runtime or packaging impact
• CLI output or machine-readable contract changed
• Workspace layout, flow state, or artifact paths changed
• Native toolchain or wrapper behavior changed
• ecc-tools or ecc-dreamplace dependency changed
• PyInstaller, Nix, or release artifact changed

Notes:

-This changes the runtime behavior of resuming existing workspaces.
-No workspace layout or artifact format is intentionally changed; the existing rerun mechanism is now used consistently by the CLI.
-No dependencies or packaging artifacts are affected.

Validation

List the commands you ran. Mark checks that are not applicable as N/A.

• uv run pytest test/
• uv run ruff check chipcompiler test
• uv run ruff format --check chipcompiler test
• PyInstaller smoke: ecc --help, ecc --version, ecc version --json
• Nix smoke: nix run .#cli -- --help
• Manual flow smoke:
• Other:

Skipped checks and reason:

Checklist

• I kept the change scoped to ECC.
• I updated docs or user-facing CLI text where behavior changed.
• I included lockfile or version metadata updates when dependencies changed.
• I documented any submodule updates and why they are needed.
• I did not include local caches, virtual environments, or generated build outputs.
• I explained skipped validation and remaining risk.