Reduce log level of unhelpful logs and allow for dynamic control of acorn log level log level of acorn

[cjellick]

This enhancement is a two parter:

• First, provide a way to dynamically set the log level of the acorn controller or api server. As an example, rancher did this via: https://github.com/rancher/loglevel/tree/master and https://github.com/rancher/log/blob/master/server/server.go. This allows an operator to run a command against the pod that will change log level with out redploying
• Second, turn the following logs down from info to debug:

time="2023-06-12T22:46:09Z" level=info msg="Handling [acorn-image-system/registry] [/v1, Kind=Service]"
time="2023-06-12T22:46:09Z" level=info msg="Triggering [acorn-system/acorn-config] [/v1, Kind=ConfigMap] from [acorn-image-system/registry] [/v1, Kind=Service]"

These logs live in mink, I believe.

[g-linville]

It should now be possible to shell into the Runtime apiserver and controller and run loglevel --set <level> to change the log level without restarting the pod.

[sangee2004]

Tested with acorn version - v0.8.0-alpha7-131-g4bf05b4d+4bf05b4d

1. Able to change log levels by executing the following command within the controller and api-server pods

kubectl exec acorn-controller-7cc79ddc88-2f5td -n acorn-system -- loglevel --set debug
kubectl exec acorn-api-55494b75d5-62msg -n acorn-system -- loglevel --set debug

2. Following logs are now logged in "debug" level:

time="2023-07-20T21:00:48Z" level=debug msg="Handling trigger [acorn-image-system/registry] [apps/v1, Kind=Deployment]"
time="2023-07-20T21:00:48Z" level=debug msg="Triggering [acorn-system/acorn-config] [/v1, Kind=ConfigMap] from [lima-rancher-desktop] [/v1, Kind=Node]"