Remove global logger from outputs and monitoring

[simitt]

What does this PR do?

Remove global logger for libbeat/outputs and libbeat/monitoring.

Why is it important?

Precondition for improved structured logging.

Checklist

• My code follows the style guidelines of this project
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have made corresponding changes to the documentation
  - [ ] I have made corresponding change to the default configuration files
  - [ ] I have added tests that prove my fix is effective or that my feature works

Author's Checklist

• Add dev changelog
• needs to be rebased once Moving outputs/transport => common/transport #16734 is merged

Related issues

• Relates Remove global logging functions in libbeat #15699

Developer Docs

Following public methods are changed to take a logger as first parameter now:

• common.transport.transport#ProxyDialer
• common.transport.tlscommon.tls#ReadPEMFile
• outputs.elasticsearch.client#BulkReadItemStatus

[urso]

@ycombinator I think parts of this interfere with your refactoring.

[simitt]

@urso , @ycombinator - yes they do, but I was already done with the changes when I saw the other PR. Don't worry about it, I will just rebase my PR once the other one is merged.

[ycombinator]

Thanks @urso, @simitt. Pretty sure this PR here will go in before the refactoring one, given their relative sizes. So please go ahead here and I will incorporate your changes into my larger refactoring PR once this PR here is merged.

[simitt]

Failing tests seem unrelated.

[urso]

@simitt all CI failures are some know collateral from the switch to go modules. Related tests are all green.

Reading through the PR I found a many places where errors are logged with %v only. Please change these to use %+v. Zap does not handle errors well or in an uniform manner, especially if errors are nested. In case of nested errors there is a high chance that the cause is not logged when using %v. Some error types implement a custom fmt.Formatter, and will only print the cause if the + flag is parsed.

[urso]

LGTM.

Thank you for taking the time and doing so many changes at once!

[simitt]

@urso I rebased my PR on top of the changes of #16734, can you please re-review the changes from the last two commits.

[urso]

LGTM