fix(sendconfig) suppress deck diff logs at info

[rainest]

What this PR does / why we need it:
Disable deck's full diff output at log level info and above. diffs will only print at debug or trace.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #2411

Special notes for your reviewer:
deck doesn't run this output through the regular logging pipeline, so it has no log level, and is controlled independently by the --silence-events flag.

I opted to limit it to debug and lower since AFAIK it doesn't have any type-specific logic for anything other than Konnect Documents, so it prints changes to certificates and credentials and such, which we don't want at info.

Ideally deck would return diff text to a callers to allow them to determine how to print it (so we could pass it through our logger while the deck CLI does what it does currently), but as it's a direct call to console print from the diff loop, we can only suppress these logs, not add proper level/timestamp/fields formatting (multi-line output makes that a pain even if we could).

PR Readiness Checklist:

Complete these before marking the PR as ready to review:

• the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

[rainest]

For comparison from a manual run:

time="2022-04-19T20:38:59Z" level=debug msg="sending configuration to Kong Admin API"
updating route default.httpbin.00  {
   "https_redirect_status_code": 426,
   "id": "d63e3f12-ab1a-4cb2-81be-6a1b69a86111",
   "name": "default.httpbin.00",
   "path_handling": "v0",
   "paths": [
-    "/httpbina"
+    "/httpbinb"
   ],
   "preserve_host": true,
   "protocols": [
     "http",
     "https"
   ],
   "regex_priority": 100,
   "request_buffering": true,
   "response_buffering": true,
   "service": {
     "id": "a043ce1c-c107-4647-8cbf-ea9db51db307"
   },
   "strip_path": false,
   "tags": [
     "managed-by-ingress-controller"
   ]
 }

time="2022-04-19T20:38:59Z" level=info msg="successfully synced configuration to kong."

time="2022-04-19T20:40:16Z" level=info msg="successfully synced configuration to kong."
time="2022-04-19T20:40:19Z" level=error msg="failed to fetch KongPlugin: no KongPlugin or KongClusterPlugin was found" kongplugin_name=kong-id kongplugin_namespace=default
time="2022-04-19T20:40:22Z" level=error msg="failed to fetch KongPlugin: no KongPlugin or KongClusterPlugin was found" kongplugin_name=kong-id kongplugin_namespace=default
time="2022-04-19T20:40:22Z" level=info msg="successfully synced configuration to kong."
time="2022-04-19T20:40:25Z" level=error msg="failed to fetch KongPlugin: no KongPlugin or KongClusterPlugin was found" kongplugin_name=kong-id kongplugin_namespace=default

[aroundthecode]

Hi guys, thanks for the fix! Any estimated release date? I've my server under heavy log flow and I'd like to fix it asap.

[rainest]

We don't have a set release schedule, but do make pre-release builds available at https://hub.docker.com/r/kong/nightly-ingress-controller/tags?page=1&ordering=last_updated

You can use one of the recent specific date tags to get that change but not new changes we add after. There's not much else new in yet since 2.3.1 outside some Gateway API-related changes.