Problem Statement

#1242 implemented a workaround to overcome the impossibility to reference a ControlPlane in Konnect via KonnectID: the certificates are managed directly by the KonnectExtension controller and their references are set on the secret via an annotation. Once we have KonnectID references implemented, we can simplify the KonnectExtension controller and leverage the KongDataPlaneClientCertificate to provision certificates in Konnect.

Anything else

This is blocked on #1470 from #1469

Acceptance Criteria

• Certificate provisioning in Konnect is performed via KongDataPlaneClientCertificate