Need to differentiate between Conditions and regular TaskRuns in PipelineRun view

[AlanGreene]

Expected behavior

It should be clear from looking at the PipelineRun view when a TaskRun has failed.

Actual behavior

Failed Conditions look like failed TaskRuns which can be a little confusing, especially if the PipelineRun has completed successfully.

Additional Info

We should consider how best to differentiate Conditions from other TaskRuns. In case of success this is probably less important, but for failed Conditions it should be clear they're not a regular failed TaskRun. Perhaps this can be done by changing the status displayed from 'Failed' to 'ConditionFailed' or similar, along with changing from the red highlight to orange / yellow (see Carbon color usage guidelines).

When we resolve #1263 it would be great to indicate the relationship between TaskRuns and Conditions so a user can easily see which TaskRuns were skipped and why.

[AlanGreene]

Tracked in #1445