logging best practice

[emanuel-schmid]

Changes proposed in this PR:

• add a novel config value logging.climada_style that controls whether or not the logging is configured in the traditional climada style.

This PR fixes #265

PR Author Checklist

• Read the Contribution Guide
• Correct target branch selected (if unsure, select develop)
• Descriptive pull request title added
• Source branch up-to-date with target branch
• Documentation updated
• Tests updated
• Tests passing
• No new linter issues
• Changelog updated

PR Reviewer Checklist

• Read the Contribution Guide
• CLIMADA Reviewer Checklist passed
• Tests passing
• No new linter issues

[tovogt]

Thanks @emanuel-schmid, this implementation looks very clean to me!

I would be happy if somebody came up with a more fitting name for the config parameter instead of logging.climada_style but I have no strong feelings. It just seems to me like it's not about the "style" of the logging, but about whether climada is in control of the logging, or whether control of the logging is left to the user. Maybe logging.managed?

[emanuel-schmid]

Thanks @tovogt . Changed it to managed - not to close the discussion, just because it's already much better.

[tovogt]

I'm happy with this PR conceptually. Please just don't forget to update the name of the config parameter ("managed" or "climada_style" or whatever) in the CHANGELOG and in the docs, once the decision for the name is final.