Refactor/logging

[schroedk]

The proposed logging is described here.

This refactoring introduces the following abstractions:

• LogOptions (implementation SQLiteLogOptions), configuration
• LogStore(implementation _SQLiteLogStore, not exposed), write access
• LogReader (implementation SQLiteLogReader), read access

The old class OptimizationLogReader redirects to SQLiteLogReader in a backward-compatible way.

[review-notebook-app[bot]]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 94.16283% with 38 lines in your changes missing coverage. Please review.

Project coverage is 90.90%. Comparing base (354155d) to head (3d815fc). Report is 1 commits behind head on 0.5.0.

Files	Patch %	Lines
src/optimagic/logging/base.py	85.71%	11 Missing :warning:
src/optimagic/logging/logger.py	95.34%	10 Missing :warning:
src/optimagic/logging/sqlalchemy.py	95.56%	7 Missing :warning:
src/optimagic/typing.py	84.09%	7 Missing :warning:
src/optimagic/optimization/multistart.py	71.42%	2 Missing :warning:
...imagic/optimization/create_optimization_problem.py	90.90%	1 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## 0.5.0 #519 +/- ## ========================================== + Coverage 90.71% 90.90% +0.18% ========================================== Files 106 107 +1 Lines 10364 10644 +280 ========================================== + Hits 9402 9676 +274 - Misses 962 968 +6 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[schroedk]

I am through now. Thanks a lot for this PR!

One thing that is left to do is adding a logger field to the OptimizeResult.

Done