Avoid adding test flags when using the null logger

The null logger from logr is in the same package as the testing logger,
which means it accidentally adds testing flags to all binaries that
import it.  Copy the null logger into the pkg/runtime/log package
to avoid this.

Author: DirectXMan12

pkg/runtime/log/log.go

@@ -6,7 +6,6 @@ import (
 	"log"
 
 	"github.com/go-logr/logr"
-	tlogr "github.com/go-logr/logr/testing"
 	"github.com/go-logr/zapr"
 	"go.uber.org/zap"
 )
@@ -45,7 +44,7 @@ func SetLogger(l logr.Logger) {
 // to another logr.Logger.  You *must* call SetLogger to
 // get any actual logging.
 var Log = &DelegatingLogger{
-	Logger:  tlogr.NullLogger{},
+	Logger:  NullLogger{},
 	promise: &loggerPromise{},
 }
 

pkg/runtime/log/null.go

@@ -0,0 +1,39 @@
+package log
+
+import (
+	"github.com/go-logr/logr"
+)
+
+// NB: this is the same as the null logger logr/testing,
+// but avoids accidentally adding the testing flags to
+// all binaries.
+
+type NullLogger struct{}
+
+var _ logr.Logger = NullLogger{}
+
+func (_ NullLogger) Info(_ string, _ ...interface{}) {
+	// Do nothing.
+}
+
+func (_ NullLogger) Enabled() bool {
+	return false
+}
+
+func (_ NullLogger) Error(_ error, _ string, _ ...interface{}) {
+	// Do nothing.
+}
+
+func (log NullLogger) V(_ int) logr.InfoLogger {
+	return log
+}
+
+func (log NullLogger) WithName(_ string) logr.Logger {
+	return log
+}
+
+func (log NullLogger) WithValues(_ ...interface{}) logr.Logger {
+	return log
+}
+
+