✨ Add option for json log format to OCM Status Add-On ctlr+agent

[MikeSpreitzer]

Summary

This PR extends the set of log formats available from just "text" to also include "json".

Related issue(s)

Fixes #

[MikeSpreitzer]

After this change:

mspreitz@mjs13 ocm-status-addon % go run ./cmd/ocm-status-addon controller -h
Start the addon controller

Usage:
  addon controller [flags]

Flags:
      --component-namespace string   Namespace of the component.
      --enable-leader-election       Enables the leader election for the controller
  -h, --help                         help for controller
      --kubeconfig string            Location of the master configuration file to run from.

Global Flags:
      --log-flush-frequency duration         Maximum number of seconds between log flushes (default 5s)
      --log-json-info-buffer-size quantity   [Alpha] In JSON format with split output streams, the info messages can be buffered for a while to increase performance. The default value of zero bytes disables buffering. The size can be specified as number of bytes (512), multiples of 1000 (1K), multiples of 1024 (2Ki), or powers of those (3M, 4G, 5Mi, 6Gi). Enable the LoggingAlphaOptions feature gate to use this.
      --log-json-split-stream                [Alpha] In JSON format, write error messages to stderr and info messages to stdout. The default is to write a single stream to stdout. Enable the LoggingAlphaOptions feature gate to use this.
      --logging-format string                Sets the log format. Permitted formats: "json" (gated by LoggingBetaOptions), "text". (default "text")
  -v, --v Level                              number for the log level verbosity
      --vmodule pattern=N,...                comma-separated list of pattern=N settings for file-filtered logging (only works for text log format)

Before this change, the json stuff was not there.