Follow-up APIBindings: have more speaking names of CRDs in shadow namespace

[sttts]

Follow-up of #417.

Problem: the names of CRDs in the system:bound-crds workspace have cryptic names. For debugging it would be very helpful to have the resource and group name plus the uid there.

Also see #702 (comment) for details.

[sttts]

cc @ncdc

[ncdc]

What about having that data in labels or annotations? Or you think a more meaningful name is needed?

[sttts]

I think name is better as it shows up in controller logs for example. This is not about technically being able to find the objects, but rather as a human to understand what these 300 CRDs mean there.

[ncdc]

Makes sense. Will resource+group+uid fit within the maximum name length limit?

[sttts]

Good question. Probably 63 chars for names. And that can be exhausted for a resource name alone I guess. But something like resource.group-<8-alpha-numeric-chars> is probably good enough. We can have a deterministic shortening of resource.group in case it's getting too long.