feat: Improve metrics collected during benchmarks

[maxep]

What and why?

Memory and CPU metrics were only reporting the last values collected after 10 s interval. It cannot provide accurate data, instead we are now collecting metrics more frequently and report the aggregated values during push.

How?

Collect CPU usage and Memory footprint using timers configured to read values every 100 ms, then report the aggregation depending on the metric type:

• The max memory footprint
• The average CPU usage
• The min frame rate.

Review checklist

• Feature or bugfix MUST have appropriate tests (unit, integration)
• Make sure each commit and the PR mention the Issue number or JIRA reference
• Add CHANGELOG entry for user facing changes

[mariedm]

Looks great! 🙌

General question: do you know the impact of the more frequent metric collection on the app's performance?

[mariedm]

I was wondering if we could merge these two extensions since the logic inside is the same, but it doesn't seem straightforward.

[maxep]

I tried, but failed :/ Problem is that there is 2 distinct Double.init that take either a BinaryInteger or a BinaryFloatingPoint. There is no common method that can help computing the avg value.