Pipeline start action is disabled for users who have view access to pipeline

Description of problem:

Customer wants to prevents non-technical users from modifying or creating pipelines but still allow then to start the existing pipelines. They have created a role that gives "view" access to "Pipeline" resources and "create" access to "PipelineRun" and "TaskRuns". The outcome is that the kebab menu shows the "Start" action as disabled and still does not allow users to start the pipeline even thought they have access to do so. The "Start Last Run" action shows enabled in this scenario.

Steps to Reproduce

• Create a role with "view" access on "Pipeline" and "create" access on "PipelineRun" and "TaskRun"
• Login as a user that has the above role
• Go to a namespace with an exist pipeline and click on the Pipelines in the nav
• Click on the kebab menu of the existing pipeline

Actual results:

"Start" is disabled while "Start Last Run" is enabled. The rest of actions are disabled.

Expected results:

"Start" and "Start Last Run" are enabled while the rest of actions are disabled.