Remove unused results field from pr and tr specs

[dibyom]

Changes

Fixes #1243
The results field is unused, was deprecated in 0.7, and was
scheduled to be removed in the 0.8 release

Co-authored-by: Daniel Helfand [email protected]
Signed-off-by: Dibyo Mukherjee [email protected]

Submitter Checklist

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

• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices

Release Notes

The `results` field has been removed from the TaskRun and PipelineRun spec

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[ghost]

/lgtm

[tekton-robot]

The following is the coverage report on pkg/.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/apis/pipeline/v1alpha1/pipelineresource_validation.go	89.4%	88.7%	-0.7
pkg/apis/pipeline/v1alpha1/pipelinerun_validation.go	89.5%	93.8%	4.3
pkg/apis/pipeline/v1alpha1/taskrun_validation.go	91.3%	95.3%	4.0
pkg/reconciler/pipelinerun/pipelinerun.go	82.7%	82.6%	-0.1

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

[dibyom]

Daniel has previously committed to pipelines so I'm guessing its the co-authorship that messed up the CLA

[dlorenc]

/approve

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dlorenc

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

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

[danielhelfand]

@dibyom Thanks for the co-authorship!