Convert test/cluster_resource_test.go's Tekton structs to YAML

[abayer]

Changes

Part of #4276

This is just one file from test/..., but it seemed like a good "let's start here" case to make sure the approaches I've gone with are acceptable:

• To deal with cases where we're parameterizing the struct currently, this keeps the parameterizing, using fmt.Sprintf(...), since I decided that the raw multiline string literal was the way to go even if we need to do some %s replacement in it.
• For the moment, at least, I'm only worrying about Tekton structs - so the Secret and ConfigMap used in this test I just leave as is, rather than changing them to YAML. If y'all feel we should move those too, well, I'll do that. =)

/kind cleanup

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Docs included if any changes are user facing
• Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including
  functionality, content, code)
• Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes

NONE

[abayer]

/wip
/assign @vdemeester @pritidesai

[abayer]

#4286 fixes the flaky pkg/reconciler/taskrun/taskrun_test.go TestReconcile/params failure, fwiw.

[pritidesai]

/test pull-tekton-pipeline-alpha-integration-tests
/test pull-tekton-pipeline-integration-tests

[pritidesai]

To deal with cases where we're parameterizing the struct currently, this keeps the parameterizing, using fmt.Sprintf(...), since I decided that the raw multiline string literal was the way to go even if we need to do some %s replacement in it.

This will be helpful in most of the tests since some of the artifacts including names are auto generated.

For the moment, at least, I'm only worrying about Tekton structs - so the Secret and ConfigMap used in this test I just leave as is, rather than changing them to YAML. If y'all feel we should move those too, well, I'll do that. =)

You decide 😄 I think we can if we have many occurrences of secrets and ConfigMaps. For now, this is great.

/approve

[abayer]

@pritidesai - ok! If I hit enough other corev1 structs in test/..., I'll switch them to YAML, but I won't worry about that to start. Next PR up in the chain after this one is going to switch all of Task, TaskRun, Pipeline, PipelineRun, and PipelineResource to YAML, so it may take a few days.

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pritidesai, 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 [pritidesai,vdemeester]

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

[afrittoli]

Nice, thank you!
/lgtm