Consistent Approach to Referring to Tekton Resources Through CLI

[danielhelfand]

We should have a consistent approach to how resources are referenced in tkn. Currently, there are several different approaches used. An example is TaskRun:

TaskRun:

cli/pkg/cmd/taskrun/list.go

Line 36 in 84e7da6

emptyMsg = "No TaskRuns found"

taskrun:

cli/pkg/cmd/taskrun/list.go

Line 82 in 84e7da6

fmt.Fprintf(os.Stderr, "Failed to list taskruns from %s namespace \n", p.Namespace())

Taskrun:

cli/pkg/cmd/task/start.go

Line 239 in 4ae08d7

fmt.Fprintf(opt.stream.Out, "Taskrun started: %s\n", trCreated.Name)

My thought would be to capitalize the resource name (TaskRun) or to lowercase the resource name completely (taskrun).

While I am using TaskRun as an example, this applies to all resources in the CLI. I have no preference on how to refer to resources, but we should be consistent throughout the CLI.

[danielhelfand]

/kind cleanup

[chmouel]

Camel case names i.e: TaskRuns feels more natural to me!

[danielhelfand]

/assign