feat: add logger

[marvinmarnold]

Why
It is helpful to have verbose logs that are consistent across all services.

How
This logger has been copied from hm-config.

[vpetersson]

Accepted with minor comment.

[vpetersson]

Needs to be:

• pip install -r requirements.txt
• pip install -r test-requirements.txt

[marvinmarnold]

Thanks, fixed: 9d9d1d8

[vpetersson]

Don't think the explicit PYTHONPATH is required here.

[marvinmarnold]

I'm unsure if this is a best practice but with the code as-is now, you'll get an error if just trying to pytest. This type of thing is a problem whenever we have the test code in a separate directory/module. In other repos, we get around it by modifying the path from the test code, which I think is worse.

✗ pytest
========================================== test session starts ===========================================
platform linux -- Python 3.7.3, pytest-6.2.5, py-1.10.0, pluggy-1.0.0
rootdir: /home/user/code/nebra/hm-pyhelper
collected 10 items / 1 error / 9 selected                                                                

================================================= ERRORS =================================================
________________________ ERROR collecting hm_pyhelper/tests/utils/test_logger.py _________________________
ImportError while importing test module '/home/user/code/nebra/hm-pyhelper/hm_pyhelper/tests/utils/test_logger.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/home/user/.pyenv/versions/3.7.3/lib/python3.7/importlib/__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests/utils/test_logger.py:2: in <module>
    from utils.logger import get_logger, _log_format

[vpetersson]

pwd should be in PYTHONPATH, but this is not a big deal.

[vpetersson]

LGTM, but i think you need to merge in master and bump up the version.

[marvinmarnold]

This had to be bumped twice because of this: #20

[vpetersson]

@marvinmarnold FYI - to release you need to create a git tag for the release (e.g. v0.6.3), push this and then generate a release in GitHub. The new release will then be built and pushed to PyPi.