Add rendering for retried taskRuns

[steveodonovan]

Changes

#936

Adds a rendering for taskRun retries.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide
for more details.

One thing to follow up on. Why do we sort by step started time on the taskRun tree. https://github.com/tektoncd/dashboard/blob/master/packages/components/src/components/PipelineRun/PipelineRun.js#L67

The values can be blank - below is a sample

conditions:
  - type: Succeeded
    status: Unknown
    lastTransitionTime: '2020-05-26T16:14:42Z'
    reason: Pending
    message: >-
      pod status "Ready":"False"; message: "containers with unready status:
      [step-task-one-step-one step-task-one-step-two]"
podName: sample-piperun-on-tenbase7-task2-hjrw2-pod-xh4n6
startTime: '2020-05-26T16:14:39Z'
steps:
  - waiting:
      reason: PodInitializing
    name: task-one-step-one
    container: step-task-one-step-one
  - waiting:
      reason: PodInitializing
    name: task-one-step-two
    container: step-task-one-step-two

[AlanGreene]

Why do we sort by step started time on the taskRun tree

Some of the discussion about the sorting is on the original PR here #1077 but I don't think it was all captured 😿 There was an issue with the TaskRun times in some cases, but we've had Tekton Pipelines 0.11 and 0.12 released since then (end of Feb) with many potentially relevant changes in that area so probably worth revisiting that decision.

[AlanGreene]

suggestion on the string id, otherwise code looks good
testing this out now and so far it's working great!

[AlanGreene]

Suggested change

	id: 'dashboard.pipelineRun.pipelineTaskName.retryAppendage',
	id: 'dashboard.pipelineRun.pipelineTaskName.retry',

[AlanGreene]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AlanGreene

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:

• OWNERS [AlanGreene]

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