my.core.logging: compatibility with HPI_LOGS

[purarue]

I had tried to set the DEFAULT_LEVEL like we discussed in #305 here:

HPI/my/core/logging.py

Line 49 in c283e54

DEFAULT_LEVEL = 'INFO'

But if the module had already set a level like:

from my.core import make_logger

logger = make_logger(__name__, level="warning")

then any attempt to use HPI_LOGS (which would use the DEFAULT_LEVEL) would be ignored, which is not what the user would expect (they'd expect the --debug flag to just override everything)

So, added a check after the LOGGING_LEVEL_ check in the get_env_level function instead

[karlicoss]

Thanks, looks good!
Only thing I'm thinking is that LOGGIN_LEVEL* and HPI_LOGS have inconsistent naming. Perhaps we could use LOGGING_LEVEL_HPI as the primary control instead, and use HPI_LOGS as a legacy fallback? Not a huge deal though.

[purarue]

Yeah, I think I mentioned the same in #305, can update the docs to something more consistent

[purarue]

Should be good, added a my.core.warnings.medium incase the user had HPI_LOGS set