Adding logic to allow namespace metadata to be honoured on destination

[ayetealab]

Summary

Propagate Namespace Metadata on Creation

This PR introduces optional propagation of namespace metadata (labels and annotations) from KCP workspaces into destination workload clusters during namespace creation.

• Default behavior remains unchanged — namespaces are still created in a "one-and-done" manner with no metadata, unless the APIExport and APIBinding explicitly expose and grant permission claims for namespaces.
• When permitted, the sync-agent will copy labels and annotations from the source namespace into the destination namespace at creation time.
• No ongoing sync of namespace metadata is introduced - namespaces are not promoted to first-class sync targets.

What Type of PR Is This?

/kind feature

Related Issue(s)

Fixes #97

Release Notes

NONE

[kcp-ci-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign embik for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kcp-ci-bot]

Hi @ayetealab. Thanks for your PR.

I'm waiting for a kcp-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.