Add catching of `record=True`

[kornicameister]

Ref: #6
Ref: python/mypy#9010

This is basically an extension of what was implemented for #6. With record=True user can access special dictionary inside of a template. record=False basically means opposite so user should be told that he is doing the wrong thing for both of cases;

logger.info('{record["msg"]}') # bad
logger.opt(record=True).info('{record["msg"]}') # ok

[issue-label-bot]

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.95. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[kornicameister]

@Delgan is following possible

logger.opt(record=True).info('record={record}', record=lambda : {})

?

[Delgan]

@Delgan Nope, it raises an error.

>>> from loguru import logger
>>> logger.opt(record=True).info('record={record}', record=lambda : {})
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "loguru/_logger.py", line 1971, in info
    __self._log("INFO", None, False, __self._options, __message, args, kwargs)
  File "loguru/_logger.py", line 1934, in _log
    raise TypeError(
TypeError: The message can't be formatted: 'record' shall not be used as a keyword argument while logger has been configured with '.opt(record=True)'

[kornicameister]

Alright, so we have another thingy to enforce ;-)