logger errors in recent main builds

[kishorj]

Describe the bug
The controller built from the main branch contain the following errors in the logs

 {"level":"dpanic","ts":"2023-02-10T19:23:18Z","msg":"odd number of arguments passed as key-value pairs for logging","ignored key":["controller","ingress"]}
{"level":"dpanic","ts":"2023-02-10T19:23:18Z","msg":"odd number of arguments passed as key-value pairs for logging","ignored key":["controller","service"]}
{"level":"dpanic","ts":"2023-02-10T19:23:18Z","msg":"odd number of arguments passed as key-value pairs for logging","ignored key":["controller","targetGroupBinding"]}
{"level":"dpanic","ts":"2023-02-10T19:23:18Z","msg":"odd number of arguments passed as key-value pairs for logging","ignored key":["controllerGroup","elbv2.k8s.aws","controllerKind","TargetGroupBinding"]} 

Steps to reproduce
Build and deploy controller from the main branch

Expected outcome
The panic logs are not there

Environment

• AWS Load Balancer controller version - main builds
• Kubernetes version - 1.24
• Using EKS (yes/no), if so version?, Yes, 1.24

Additional Context:
Related to changes from PR #2998, go-logr incompatible with controller-runtime?