Add logging guidelines for developers

[pleshakov]

Proposed changes

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

Note:
I included a temp doc with a list of issues I see that are spawned by the guidelines. They show the diff between the guidelines and the code. I didn't want to add them before the PR is reviewed and merged, as they might change because of that.

UPDATE: Issues were created:
Added issues:

• Inject Loggers according to the guidelines #918
• Inject Loggers according to the guidelines #918
• Support Log Levels #919
• Support control plane logging configuration for developers #922
• Bring consistency into logging #920
• Ensure Critical Errors are logged Before Termination #921
• Ensure Logs are Flushed on Panics #923
• Ensure Logs are Parsable #924
• Enforce logging guidelines through linting #926

Checklist

Before creating a PR, run through this checklist and mark each as complete.

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have checked that all unit tests pass after adding my changes
• I have updated necessary documentation
• I have rebased my branch onto main
• I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

[ciarams87]

👍🏼

[pleshakov]

Added issues:

• Inject Loggers according to the guidelines #918
• Inject Loggers according to the guidelines #918
• Support Log Levels #919
• Support control plane logging configuration for developers #922
• Bring consistency into logging #920
• Ensure Critical Errors are logged Before Termination #921
• Ensure Logs are Flushed on Panics #923
• Ensure Logs are Parsable #924
• Enforce logging guidelines through linting #926