epic: support syncing associated resources in kube-bind

[mirzakopic]

Description

To make the syncing in kube-bind truly useful, it needs support to sync "associated" resources. This means mostly objects that are referenced in the main resources exposed via kube-bind (think of a secretRef or a configMapRef). Syncing can happen in both directions (either you pass an object as reference because it extends the spec config of a resource, or you get an object back as a result of reconciliation).

There is an existing PR at kbind-dev/kbind#185. It would be good to get in touch with the author and see if we can take it over or push it forward.

Objectives

•  Users and implementors of the kube-bind protocol should be able to sync objects associated with the API objects shared via kube-bind

Stories

• Look at Claimed resources api kbind-dev/kbind#185 and see if it can be re-used. Get in touch with the original author
• Work on finalising implementation and getting it merged
• Extend kcp kube-bind backend (feature: make order of authorizers configurable #2) with it

Demo Required

Yes

Demo Steps

No response

Migrated from openmcp/kcp-upstream#17

[mjudeikis]

replaced by kbind-dev/kbind#316 which is already inprogress