Description of problem:

When the user have multiple pipelines and show them in the Pipeline list and the user re-run one of the latest this pipeline "jumps around".

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

1. OpenShift Pipelines Operator (tested with 1.2.3)

Steps to Reproduce

1. Create at least two pipelines

apiVersion: tekton.dev/v1beta1
kind: Pipeline
metadata:
  name: sometimes-failing
spec:
  tasks:
    - name: sometimes-failing
      taskSpec:
        steps:
          - name: sometimes-failing
            image: node
            script: |
              #!/bin/bash
              sleep 10
              if (( RANDOM % 2 )); then
                exit 0
              else
                exit 1
              fi

1. Run and finish Pipeline 1
2. Run and finish Pipeline 2
3. Actual and expected order: Pipeline 2 is shown above Pipeline 1
4. Run Pipeline 2 again
5. Go back to the Pipeline list page

Actual results:

1. Pipeline 2 is now shown at the end of the Pipeline list while running (jumps down) and after running at the top of the list again (jumps up again).

Expected results:

1. Pipeline 2 is shown above Pipeline when Running and when finished.
2. Pipeline 2 shows a last run time about the current running Pipeline Run.

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

4.8 frontend (master, commit e63847533cc78d1ee883c334d215dda21d23745b)
on a 4.6.9 OpenShift (crc) with OpenShift Pipelines Operator 1.2.3

Additional info:

The tkn cli shows the last run time (as "Started") also for running Pipelines.

The pipeline detail page shows also a last run time (Started) for the latest Pipeline Run and show this on top of the list.