Add dynamic metric selection and results display to evaluation UI

[Aki-07]

Fixes #162

[Aki-07]

@boyangsvl requesting for review

[boyangsvl]

Yifan could you help to review?

[wyf7107]

Sure, will take a look

[wyf7107]

Hi @Aki-07 , do you mind resolving the quick conflict? I then can pull this down and test it locally, thanks!

[Aki-07]

Hey @wyf7107, have solved the conflicts, do check out

[wyf7107]

Thanks! Willl reivew great work!

[lmurawski-equinix]

Thanks! Willl reivew great work!

hi @wyf7107, can you review and merge please.

[majsterkovic]

Hi @Aki-07,

Thank you for this PR! It’s a very much-needed feature. However, I encountered several compilation errors when trying to run it locally. It seems like there are some duplicate imports and missing definitions, likely due to a merge conflict or incomplete cleanup.

Here is the list of issues preventing the build:

1. Duplicate Identifiers in eval-tab.component.ts:
   The following components are imported twice (e.g., around lines 19-26 and again in lines 42-45), which causes TS2300 errors:

• NgClass
• MatIcon
• MatProgressSpinner
• MatTooltip

3. Missing ChangeDetectionStrategy:
   In eval-tab.component.ts, ChangeDetectionStrategy.OnPush is used in the @component decorator, but ChangeDetectionStrategy is not included in the imports from @angular/core.

4. Service Method Missing / Type Mismatch:
   The compiler reports that listMetricsInfo does not exist on EvalService. Please ensure that src/app/core/services/eval.service.ts is fully updated and consistent with the calls made in the component.

5. Strict Type Errors in run-eval-config-dialog.component.ts:
   Methods getMin(metric), getMax(metric), and getStep(metric) are causing assignment errors (NG2) because they can return undefined. Adding a nullish coalescing operator (e.g., ?? 0) would resolve these strict type checks.