feature: sync status of related resources

[dakraus]

Feature Description

Right now, the api-syncagent does not synchronize the status of related resources at all - the
objectSyncer for related resources is always instantiated with syncStatusBack: false.

For related resources with origin: kcp, it would be benificial to have the status also available
in the service cluster so I can retrieve information from the status field and use it to
construct the primary object (e.g. an AWS Subnet publishes its ID in the status that I need to
provision an EC2 instance).

For related resources with origin: service, I do not have a concrete use case in mind right now,
but eventually it could also make sense to sync the status back to kcp.

Proposed Solution

Provide the possibility to sync the status of related resources (maybe by adding a new field in the PublishedResource):

• origin: kcp: status is synced from kcp to service cluster
• origin: service: status is synced from service cluster to kcp

Alternative Solutions

No response

Want to contribute?

• I would like to work on this issue.

Additional Context

No response