Log format unification for kyma module controllers

[kwiatekus]

Description
Adjust logging in cap-operator, so that deployments labelled with kyma-project.io/module=cap-operator produce logs that are compliant with recommendations documented here.

Reason
Our goal is unify log format in order to reduce the time needed for users and support engineers to create error and warning log dumps.
kyma-project/cli#2651

Expected logs

• make all log entries JSON parsable
• include level : debug, info, warning, error
• include timestamp (not ts) in RFC3339 format
• include message (not msg)

Actual logs

{"level":"info","ts":"2025-10-24T10:36:03Z","logger":"controller-runtime.metrics","msg":"Starting metrics server"}
{"level":"info","ts":"2025-10-24T10:36:03Z","logger":"controller-runtime.metrics","msg":"Serving metrics server","bindAddress":":8080","secure":false}
{"level":"info","ts":"2025-10-24T10:36:03Z","msg":"starting server","name":"health probe","addr":"[::]:8081"}
I1024 10:36:03.874544       1 leaderelection.go:257] attempting to acquire leader lease cap-operator-system/cap-operator.sme.sap.com...
I1024 10:36:19.532080       1 leaderelection.go:271] successfully acquired lease cap-operator-system/cap-operator.sme.sap.com
{"level":"info","ts":"2025-10-24T10:36:19Z","msg":"Starting EventSource","controller":"capoperator","controllerGroup":"operator.sme.sap.com","controllerKind":"CAPOperator","source":"channel source: 0xc00015b730"}
{"level":"info","ts":"2025-10-24T10:36:19Z","msg":"Starting EventSource","controller":"capoperator","controllerGroup":"operator.sme.sap.com","controllerKind":"CAPOperator","source":"kind source: *v1alpha1.CAPOperator"}

[Pavan-SAP]

The CAP Operator itself only emits structured logs for a while now.
From the logs.. this seems to be from the manager. Perhaps we need to initialize the logger for some of the controller-runtime related aspects. Moved to lifecycle repo.

Seems to be a known behaviour as of now: kubernetes-sigs/controller-runtime#2656