Description of problem:
Sorting TaskRuns by duration sorts the completion time instead of the actual duration. For example, a TaskRun with duration "6 minutes 5 seconds" may appear above "50 seconds," and "3 minutes 10 seconds" may appear below "1 minute 5 seconds."

Prerequisites (if any, like setup, operators/versions):

• OpenShift version: 4.16.36

• OpenShift Pipelines (Red Hat) version: 1.18.0

Steps to Reproduce:

1. Have multiple TaskRuns with a wide range of durations (from seconds to several minutes).

1. Navigate to:
   https://console-openshift-console.../pipelines/all-namespaces/task-runs?orderBy=desc&sortBy=Duration

1. Observe the order of the TaskRun durations in the list.

Actual results:

• TaskRun durations are not sorted by elapsed time but by their completion time.

• This results in incorrect ordering, e.g., "6 minutes 5 seconds" shown above "50 seconds."

Expected results:

• TaskRuns should be sorted based on the actual elapsed time in seconds (or equivalent numeric representation), not by their completion time.

Reproducibility (Always/Intermittent/Only Once):
Always