Dogfooding TaskRun names do not fit inside Result name lengths about results HOT 2 CLOSED

The issue here is that both the Results API and k8s object names approximately follow RFC 1123, which has a max length of of 63 chars. If we want to support <type>-<name> syntax, we'll need to either bump the max allowed length to 127 (63+1+63) or use a different strategy for selecting default names.

from results.

Few options I'm considering at the moment:

1. Use object UIDs. This has the benefit of dealing with delete + apply iterations gracefully, but loses out on human recognizable names.
2. Drop the type prefix, and only use the name. Since k8s resource names will be <= 63 chars, this will make it compatible with the current results constraints, but this means that we can't distinguish taskruns from pipelineruns, so if a pair of objects share the same name they will be automatically grouped in the same result by default (which might be unintended in some cases).
3. Expand the constraints to allow for type + name. While this would allow us to keep the same semantics as we have right now, this means that names could potentially be up to 63+len('/results/')+127+len('/records/')+127 = 335, which seems excessive.

from results.