Support showing how a PipelineRun was triggered

[andrewballantyne]

Fixes:
https://issues.redhat.com/browse/ODC-3323

Analysis / Root cause:
With the addition of Tekton Triggers, we now have a desire to separate who started a Pipeline Run... was it the Trigger or a user?

Solution Description:
Two fold solution:

• For Manual starts - Inject the username into the labels of a Pipeline Run as it is created to carry forward who started it
• For Trigger kicks - Read the provided label from the Operator to link back to the Event Listener

Screen shots / Gifs for design review:

@openshift/team-devconsole-ux

Unit test coverage report:

• Figure out what unit tests, if any we can write here (most functionality is hooks)

Test setup:

• Install the Pipeline Operator
• Manually triggering a Pipeline from any button in the UI should tag the username onto the PLR as it is created
• Installing a Trigger and executing it will show the resource link (see me if you need some resources / steps to get up and running fast to test this)

Browser conformance:

• Chrome
• Firefox
• Safari
• Edge

[karthikjeeyar]

Tested it with developer user, it works fine.

[karthikjeeyar]

Looks like some of the tests are failing here.

[karthikjeeyar]

Verified both the manual and trigger scenario, works fine.

[karthikjeeyar]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andrewballantyne, karthikjeeyar

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• frontend/packages/dev-console/OWNERS [andrewballantyne]

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

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andrewballantyne, karthikjeeyar

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• frontend/packages/dev-console/OWNERS [andrewballantyne]

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

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.