SRVKP-5501: feat: Implement support for Task spec.displayName

[aThorp96]

Implements https://issues.redhat.com/browse/SRVKP-5501

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[aThorp96]

@vikram-raj Do you mind reviewing when you are able?

[vikram-raj]

The list page uses spec.displayName, whereas the details page uses metadata.name as a user it looks broken because of difference in name. As this is a feature, can you confirm it with PM/UX?

[lokanandaprabhu]

In TaskRun list page, it still shows name instead of displayName. Is this fine?

[vikram-raj]

@lokanandaprabhu IMO, we should show displayName here if it is available in TR. wdyt @aThorp96 ?

[aThorp96]

@vikram-raj @lokanandaprabhu in that view the Task column's display name is not actually related to the Task object, but the name of the Task in the Pipeline.

This column could be changed to fallback on the Task's Display Name via the TaskRun's annotation tekton.dev/displayName, if the TaskRun is not associated with a Pipeline/PipelineRun. However I worry that could introduce further confusion since the column would then refer to two different fields, depending on the TaskRun.

[vikram-raj]

@aThorp96 @lokanandaprabhu, in my opinion, let's go with Task metadata.name in TR list page. and lets see if we get any feedback on this from the users.

[openshift-ci-robot]

@aThorp96: This pull request references SRVKP-5501 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the feature to target the "4.20.0" version, but no target version was set.

In response to this:

Implements https://issues.redhat.com/browse/SRVKP-5501

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[vikram-raj]

/lgtm

[vikram-raj]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aThorp96, vikram-raj

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 [vikram-raj]

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

[vikram-raj]

/retest

[vikram-raj]

/retest

[vikram-raj]

/retest

[openshift-ci]

@aThorp96: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e	81364fb	link	true	/test e2e

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.