Make user-facing PipelineRun condition messages more granular and debuggable as canonical error codes

[JeromeJu]

User requirements

Following up on the discussion at #6859, a mechanism of canonical error code would be preferred for error attribution for downstream users.

Current behavior

Currently, the most similar field we have during a Run status is the PipelineRun/TaskRun reason. But
For example, PipelineValidationFailed is vague in terms of it conflates many reasons i.e. invalid param array index and invalid PipelineResult see #7434 for more detail.

The following table summarizes the PipelineRunReasons that have conflated error causes:

PipelineRunReason	Is PipelineRunReason conflated
CreateRunFailed	This could be broken down into more granular reasons of why the Taskrun/CustomRun creation failed, but why did we not make this the case remains questionable.
PipelineValidationFailed	Decompose conflated user-facing PipelineRunStatus/ TaskRunStatus failure reasons
InvalidTaskResultReference	Before taskruns are run, this shall be InvalidPipelineResultReference instead of TaskResult
InvalidPipelineResourceBindings	This is not used anymore, consider removing once v1beta1 deprecated.

The remaining questions are similar to what's discussed at #7390 , how we could not break users with such changes.

Future Work Plan

• Transform Run Condition Reasons to be debuggable as canonical error codes.

/kind question
/kind cleanup