cmd: --debug-pomerium raises only core log level, not envoy (#1441)

`--debug-pomerium` set `LogLevel=debug` but left `ProxyLogLevel` empty,
so envoy inherited debug (`firstNonEmpty(ProxyLogLevel, LogLevel,
debug)` in pkg/envoy/envoy.go), flooding logs with envoy output. Pin
`ProxyLogLevel=info` so `--debug-pomerium` raises only Pomerium core
logging; `--debug-envoy` still opts envoy into debug explicitly.

Behavior change: `--debug-pomerium` alone no longer produces envoy debug
logs.

---------

Signed-off-by: Denis Mishin <dmishin@pomerium.com>

Author: wasaga

cmd/all_in_one.go

@@ -298,6 +298,10 @@ func (s *allCmdParam) makeBootstrapConfig(opt allCmdOptions) error {
 	} else {
 		s.cfg.Options.LogLevel = "info"
 	}
+	// Keep envoy (proxy) logging at info regardless of the core log level, so
+	// --debug-pomerium raises only Pomerium core logging. --debug-envoy below
+	// opts envoy into debug explicitly.
+	s.cfg.Options.ProxyLogLevel = "info"
 	if opt.debugEnvoy {
 		s.cfg.Options.ProxyLogLevel = "debug"
 		s.cfg.Options.LogLevel = "debug"