Allow experiments table to sort by last run started

[dpanshug]

Closes: RHOAIENG-7715

Description

Added new column in Experiments table for last run started.

How Has This Been Tested?

Go to Experiments page and you can find the new column added.

Test Impact

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

• The developer has tested their solution on a cluster by using the image produced by the PR to main

@yannnz

[dpanshug]

Is blocked by RHOAIENG-7692

[codecov]

Codecov Report

Attention: Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.

Project coverage is 78.65%. Comparing base (74513a0) to head (56108da).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2890      +/-   ##
==========================================
+ Coverage   78.63%   78.65%   +0.01%     
==========================================
  Files        1120     1120              
  Lines       23772    23778       +6     
  Branches     5984     5986       +2     
==========================================
+ Hits        18693    18702       +9     
+ Misses       5079     5076       -3     

Files	Coverage Δ
...d/src/concepts/pipelines/content/tables/columns.ts	55.55% <ø> (ø)
...s/content/tables/experiment/ExperimentTableRow.tsx	100.00% <ø> (ø)
frontend/src/concepts/pipelines/kfTypes.ts	100.00% <ø> (ø)
...ipelines/content/tables/experiment/renderUtils.tsx	88.23% <83.33%> (-2.68%)	⬇️

... and 3 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 74513a0...56108da. Read the comment docs.

[dpanshug]

I've included the last_run_created_at field for the sorting in this PR. Also I've noticed that this field has been added to the experiment schema in the backend PR, so I've modified the previous functionality, which calculated the last run using the usePipelineRunsByExperiment function, to now directly use the experiment.last_run_created_at field.

Till the backend PR is merged, Last run started column will only show "Just now".

[dpanshug]

@Gkrumbach07 should we mark on this on hold, till opendatahub-io/data-science-pipelines#52 merges?

[Gkrumbach07]

@dpanshug Looks like it merged. i am testing this with the changes

[Gkrumbach07]

tested and works. there is one thing we may or may not need to handle. the backend will return "1970-01-01T00:00:00Z" on a new experiment. So we may have to handle this edge case, or they may fix it. regardless on an invalid param can you make the value -

[Gkrumbach07]

OK update from backend. Lets render "1970-01-01T00:00:00Z" and "" (empty string) as -. otherwise render as date

[Gkrumbach07]

awesome thanks

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Gkrumbach07

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• frontend/OWNERS [Gkrumbach07]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment