fix(forge): preserve debug traces when setUp reverts

[IrshadKohl51]

Motivation

forge test --debug currently only feeds Execution traces into the debugger.
When setUp() reverts, there is no execution trace, so debugger startup fails with Error: debug arena is empty and --dump cannot be used in this failure path (see #10322).

Solution

• In forge test --debug, prefer Execution traces, but fall back to available Setup/Deployment traces when execution traces are empty.
• Adjust setup tracing override logic in the runner so debug tracing is preserved for debug runs (while keeping the existing optimization for non-debug runs and invariant needs).
• Add a regression test test_debug_with_dump_setup_revert to verify:
  • --debug --dump completes when setUp() reverts,
  • dump file is generated,
  • debug arena is empty is not emitted,
  • setup failure is still reported in output.

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

[mablr]

sgtm, thanks

[figtracer]

should probably do the same for invariant runs too, everything else lgtm

[mablr]

should probably do the same for invariant runs too, everything else lgtm

@figtracer follow-up ? Is this g2g ?

[figtracer]

should probably do the same for invariant runs too, everything else lgtm

@figtracer follow-up ? Is this g2g ?

would like to get another approval from @zerosnacks