Every warning/error should provide useful context

[anselor]

Warnings/errors with generic messages do not provide context for what in the code caused the error.

Specifically, I ran into it here:

sphinx-autodoc-typehints/src/sphinx_autodoc_typehints/__init__.py

Line 343 in bf27bef

_LOGGER.warning(f"Failed guarded type import with {exc!r}")

I changed that log to also print guarded_code and it helped a lot. But I really think it should reraise the exception with the guarded_code and then catch and log it here with additional context:

sphinx-autodoc-typehints/src/sphinx_autodoc_typehints/__init__.py

Line 347 in bf27bef

_resolve_type_guarded_imports(autodoc_mock_imports, obj)

[ewjoachim]

when logging inside an except handler, it's often useful to include exc_info=True.