fix: allow sort of metrics under avg_metrics [DET-8408]

[mapmeld]

Description

Experiment page's Workloads table was having trouble sorting by metric. Discovered this was due to metrics being wrapped inside of metrics->avg_metrics since #4746 . This change attempts to sort by metrics->>key and metrics->avg_metrics->>key. For some reason I also had to cast this to a numeric type to sort by value.

Test Plan

https://determinedai.atlassian.net/browse/DET-8408 describes an experiment which generates metrics and is always sorted server-side by batch number, which then confusingly gets sorted client-side.

Checklist

• Changes have been manually QA'd
• User-facing API changes need the "User-facing API Change" label.
• Release notes should be added as a separate file under docs/release-notes/.
  See Release Note for details.
• Licenses should be included for new code which was copied and/or modified from any external code.
• If modifying /webui/react/src/shared/ verify make -C webui/react test-shared passes.

[netlify]

✅ Deploy Preview for storybook-det ready!

Name	Link
🔨 Latest commit	12c6b75
🔍 Latest deploy log	https://app.netlify.com/sites/storybook-det/deploys/632b630a521eaf000993e59c
😎 Deploy Preview	https://deploy-preview-5086--storybook-det.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify]

✅ Deploy Preview for determined-ui ready!

Name	Link
🔨 Latest commit	12c6b75
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/632b630a521eaf000993e599
😎 Deploy Preview	https://deploy-preview-5086--determined-ui.netlify.app/
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[ioga]

good catch. we need an automated test for this.

This change attempts to sort by metrics->>key and metrics->avg_metrics->>key

why is metrics->>key sorting necessary at all?

[mapmeld]

why is metrics->>key sorting necessary

Have all past and future recorded metrics been converted to metrics->avg_metrics->>key ?

[ioga]

why is metrics->>key sorting necessary

Have all past and future recorded metrics been converted to metrics->avg_metrics->>key ?

database representation of these hasn't changed, it's all in training/validation CTEs in the queries.
they either use raw metrics column for batch metrics (in which case it has avg_metrics natively), or we just pick the avg_metrics component from it using jsonb_build_object. unless there's a bug in the query, I believe it should all be metrics->avg_metrics.

[mapmeld]

@ioga - OK that works. Added a client-side fix for the remaining issue