Add logging guidelines for developers

Problem:
The project doesn't include logging guidelines. As a result, there is
risk the logging:
(1) Evolves chaotically.
(2) Not adequately addresses both users and developer needs.

Solution:
Add logging guidelines for developers.

Solves #547


Co-authored-by: Kate Osborn <50597707+kate-osborn@users.noreply.github.com>
Co-authored-by: Ciara Stacke <18287516+ciarams87@users.noreply.github.com>
Co-authored-by: Saylor Berman <s.berman@f5.com>

Author: 4 people

docs/developer/go-style-guide.md

@@ -352,12 +352,7 @@ panic(fmt.Errorf("unknown event type %T", e))
 
 ## Logging
 
-> **Note**
-> This section is a work in progress.
-
-NKG uses [logr](https://pkg.go.dev/github.com/go-logr/logr) for its logging library. Each component that logs should
-inherit their logger from the main process using
-the [`WithName`](https://pkg.go.dev/github.com/go-logr/logr#hdr-Logger_Names) function.
+See the [Logging guidelines](logging-guidelines.md) document.
 
 ## Concurrency