kyverno: [Bug] LeaderElection related logs should be Debug level instead

Kyverno Version

1.7.2

Description

While checking Kyverno logs, just noticed it prints out lots of leader election related logs:

kyverno-84ffd96fb5-fpn4p kyverno I0628 07:48:15.561563       1 round_trippers.go:553] GET https://10.233.0.1:443/apis/coordination.k8s.io/v1/namespaces/kyverno/leases/kyverno 200 OK in 3 milliseconds
kyverno-84ffd96fb5-fpn4p kyverno I0628 07:48:15.563599       1 round_trippers.go:553] GET https://10.233.0.1:443/apis/coordination.k8s.io/v1/namespaces/kyverno/leases/kyverno 200 OK in 1 milliseconds
kyverno-84ffd96fb5-fpn4p kyverno I0628 07:48:15.563740       1 status.go:31] webhookMonitor/WebhookStatusControl "msg"="annotation kyverno.io/webhookActive already set to 'true'" "name"="kyverno" "namespace"="kyverno"
kyverno-84ffd96fb5-7txh6 kyverno I0628 07:48:16.020497       1 round_trippers.go:553] GET https://10.233.0.1:443/apis/coordination.k8s.io/v1/namespaces/kyverno/leases/webhook-register 200 OK in 2 milliseconds
kyverno-84ffd96fb5-7txh6 kyverno I0628 07:48:16.025020       1 round_trippers.go:553] PUT https://10.233.0.1:443/apis/coordination.k8s.io/v1/namespaces/kyverno/leases/webhook-register 200 OK in 4 milliseconds
kyverno-84ffd96fb5-7txh6 kyverno I0628 07:48:16.025184       1 leaderelection.go:278] successfully renewed lease kyverno/webhook-register

Leader election logs prints lots of information in I level and our logging system pushes these logs to elasticsearch index storage unnecessarily.

It would be nice to set log level D (Debug) or something.

cc @developer-guy

Slack discussion

No response

Troubleshooting

• I have read and followed the documentation AND the troubleshooting guide.
• I have searched other issues in this repository and mine is not recorded.