chore(pipeline-perf): add CPU cycle metrics to perf reports

[cijothomas]

Summary

• collect container perf counters (cycles/ref-cycles/instructions) in docker monitoring
• add best-effort perf binary resolution and non-interactive install path
• include cycle metrics in integration SQL report output and gh_actions_benchmark rows
• add tests for perf stat parsing/collection helpers

Validation

• pytest tools/pipeline_perf_test/orchestrator/tests/impl/strategies/monitoring/test_perf_cycles_monitoring.py
• local 100k LRPS run reaches report output (WSL2 host does not expose hardware cycles)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.19%. Comparing base (7070b74) to head (6bee77a).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3355      +/-   ##
==========================================
- Coverage   86.20%   86.19%   -0.02%     
==========================================
  Files         739      739              
  Lines      290493   290493              
==========================================
- Hits       250430   250394      -36     
- Misses      39539    39575      +36     
  Partials      524      524              

Components	Coverage Δ
otap-dataflow	87.25% <ø> (-0.02%)	⬇️
query_engine	89.58% <ø> (ø)
otel-arrow-go	52.45% <ø> (ø)
quiver	92.19% <ø> (ø)

🚀 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.