Enable TektonResults access by system:authenticated user

[khrm]

EndUser and UI require access to TektonResult because end-user/UI needs to know properties in TektonResult.

Fix #1679

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Run make test lint before submitting a PR
• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide for more details.

Release Notes

[khrm]

/kind feature

[khrm]

/assign @vdemeester @jkandasa

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

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 [vdemeester]

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

[piyush-garg]

this should not be part of config. this should be part of result reconciler

[piyush-garg]

or may be part of results itself, through aggregate view role

[khrm]

@piyush-garg It can't be part of the results because tektonresults.operator.tekton.dev is part of the operator. We also have tektonconfig clusterrolerole and bindings for authenticated users. So it make sense to add this also.

[khrm]

How can we make it part of the results reconciler? This is more of a config think according to me.

[piyush-garg]

How can we make it part of the results reconciler? This is more of a config think according to me.

aah ohk, i read it wrongly. i thought it is crd related to results component

[piyush-garg]

/lgtm