feat: log DAG wave ordering at start of wave-based execution

[jafreck]

When running in DAG mode, the fleet orchestrator now logs the computed wave plan before executing any waves. Example output:

DAG wave plan: Wave 0 → [#10, #12] | Wave 1 → [#15] | Wave 2 → [#20, #22]

This makes it easy to verify the dependency resolution and execution order from logs without inspecting the fleet checkpoint file.

Changes:

• Added logger.info() call in runWithDag() after computing waveNumbers
• Added test: logs the DAG wave plan before executing

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.49%. Comparing base (291f453) to head (5ef2b55).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #209   +/-   ##
=======================================
  Coverage   88.48%   88.49%           
=======================================
  Files          78       78           
  Lines        9182     9185    +3     
  Branches     1482     1484    +2     
=======================================
+ Hits         8125     8128    +3     
  Misses       1034     1034           
  Partials       23       23           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.