feat(konnector): annotate synced objects with source namespace and UID

[mirzakopic]

Summary

Annotates synced objects with source metadata annotations (kube-bind.io/consumer-namespace, kube-bind.io/consumer-uid, kube-bind.io/provider-namespace, kube-bind.io/provider-uid) so that both sides of the sync can trace the origin
of synced objects. This is applied in both the claimed resources reconciler (bidirectional) and the spec reconciler (consumer → provider).

What Type of PR Is This?

/kind feature

Related Issue(s)

Fixes #315

Release Notes

Added source metadata annotations on synced objects (`kube-bind.io/consumer-namespace`, `kube-bind.io/consumer-uid`, `kube-bind.io/provider-namespace`, `kube-bind.io/provider-uid`) to allow tracing the origin of objects across provider
and consumer clusters.

[mirzakopic]

@cnvergence I tried to address your comments in the latest commit:

 1. "check both sides for annotations" (happy-case_test.go:451) — Added provider-namespace/provider-uid checks on the consumer-side object alongside the existing consumer→provider checks.
  
  2. "add expectedAnnotations map" (claimedresources_reconciler_test.go:80) — Both test files now use
  expectedAnnotations map[string]string in the test struct and assert in a loop.
  
  3. "make one generic function" (claimedresources_reconciler.go:243) — Single shared
  konnectortypes.SetSourceMetadataAnnotations() in pkg/konnector/types/types.go, used by both reconcilers.
 
  4. **"it doesn't reference (r reconciler)"* (spec_reconcile.go:257) — The receiver method is gone; the shared
  function is a plain function.

[mjudeikis]

I think test failures are legging:

provider-namespace annotation must exist on consumer object

[cnvergence]

thanks