Enhancements for feature parity with Tekton

Goal:

Enhance Tekton Pipelines support in Dev Console to better match the capabilities provided by Tekton

=====

Overview

tbd

Exploration Results

Jamboard
Step 1 : https://jamboard.google.com/d/1X5nHnJf1NTxQBHRYjg0HOngkYpMcE1Lryzrk3qj3mfA/viewer
Step 2 : https://jamboard.google.com/d/1JV2zCy3sOQ9FF4Yha09x6CFpra9Kf6gF9mcuvXhKX6c/viewer
Step 3 : https://jamboard.google.com/d/17OsYsOCjUNX_cyYOqnac0TET-MeXWYTNeaTwFfp3Czc/viewer

1. GA feature, thus should be properly documented
2. GA feature, thus need to provide enablement
3. Include in what's new RHD blog
4. Consider for stretch RHD blog

Acceptance Criteria

1. Finally tasks
   1. As a user, when looking at a pipeline visualization, I should be able to see that finally tasks are part of my pipeline
   2. As a user, when looking at a pipeline run visualization, I should be able to see that finally tasks are part of my pipeline ( and see their status )
   3. As a user, when looking at the PLR status bar, I should be able to see the status of associated finally tasks
   4. As a user, I should be able to view logs of my finally tasks in the PLR Logs tab
2. Task Run Results
   1. As a user, i should be able to see Task Run Results on the TR page. Task Run Results are a key/value pair
3. Pipeline Run Results
   1. As a user, i should be able to see Pipeline Run Results on the PLR page. Pipeline Run Results are a key/value pair
4. When / Conditional Tasks
   1. As a user looking at my pipeline visualization, I should be able to visually identify When/Conditional Tasks
   2. As a user looking at my pipeline run visualization I should be able to visually identify When/Conditional Tasks and their status, as well as if they were run or not

Design Artifacts

tbd

Slack Channel

#tmp-odc-pipelines

Notes

tbd