Extend Profiler to allow for non-timing info

[neuenfeldttj]

Description

This is a smaller PR that helps solve #18460. Timer now extends a new class called ProfileMetric. The new code works how the current profiler code works but allows a breakdown to output all information (timers and non-timers). This will be useful for plugins once plugin profiling is supported. Concurrency is also achieved by determining the timers/non-timers and aggregating accordingly. Also, enums were eliminated from the generics so that the profiler could be more extensible and support this.

Related Issues

Resolves part of #18486
Resolves part of #18460

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

❌ Gradle check result for 0086e78: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for a57cbaf: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 6cce78a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 179a190: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[reta]

Thanks for this work, @neuenfeldttj the change is really look great (at least to me), we should be close to finish it, thank you

[github-actions]

❌ Gradle check result for 0f9e007: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 60e9e77: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for d22ebd6: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for d22ebd6: null

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for d22ebd6: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[reta]

One last thing (sorry, I missed it before), but LGTM otherwise, thank you @neuenfeldttj !

[github-actions]

❌ Gradle check result for 4be314f: null

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❕ Gradle check result for 8565746: UNSTABLE

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[jed326]

Thanks @neuenfeldttj, this looks like a lot of really useful plumbing work related to profiling. I'll defer to @reta for final approval and merging, but just had one small comment.

[reta]

Thanks @neuenfeldttj , great work! Thanks @jed326 for review!