[Feature]: The benchmark ci/cd workflows should capture CPU/mem usage of components such as llm-d-router

[liu-cong]

Problem Statement

1. Make sure core components such as llm-d-router is not overloaded during the benchmark and therefore not affecting benchmark results negatively
2. Serve as a regression test to detect component regressions

Proposed Solution

the results should capture cpu/memory usage stats during the benchmark

Alternatives Considered

No response

Willingness to Contribute

Yes, I can submit a PR

Additional Context

No response