Cleanup: Store projected GVR/GVK in PublishedResource status

[xrstf]

Right now, multiple controllers need to perform the Projection to get the resources they need to process in kcp. Since projection is a relatively involved process, it would be good if the agent simply stored these values in the status of a PublishedResource.

It should store the GVR for the primary resource and all related resources. The apiresourceschema controller is probably the best location to do that.

[ntnn]

Assuming we have three clusters running api-syncagent against a kcp workspace, all three restricted only to the sync controller and APIRS and APIExport managed either manually or by another syncagent.

The PublishedResource exists in each cluster - so we'd have to let the calculation happen in the sync controller, or?

Even if we have a leader-election for the APIRS/APIExport controllers happening in the kcp workspace those controllers would only be able to update the PublishedResource in their cluster.