logging_using_handler is only used in catching_logs. Therefore it makes
sense to remove one of the many context managers from the logging
plugin.

…ager.

Also mention which hook to use instead of the deprecated
pytest_cmdline_preparse

Fix pytest-dev#3022

Code cleanup

Integrate logging_using_handler into catching_logs

Respect PYTEST_DONT_REWRITE for plugins too.

closes pytest-dev#2995

Add param annotations and types to hookspec

Improve handling of pyargs

The logger parameter of catching_logs is not used anywhere. The main
motivation for removing the logger parameter is that it removes the

logger = logger or logging.getLogger(logger)

line. IMO there are too many occurences of the string 'logg' ;)

The leak was caused by the (unused) `FixtureRequest._fixture_values`
cache.

This was introduced because the `partial` object (created to call
FixtureDef.finish() bound with the Request) is kept alive
through the entire session when a function-scoped fixture depends
on a session-scoped (or higher) fixture because of the nested
`addfinalizer` calls.

FixtureDef.finish() started receiving a request object in order to
obtain the proper hook proxy object (pytest-dev#2127), but this does not seem
useful at all in practice because `pytest_fixture_post_finalizer`
will be called with the `request` object of the moment the fixture value
was *created*, not the request object active when the fixture value
is being destroyed. We should probably deprecate/remove the request
parameter from `pytest_fixture_post_finalizer`.

Fix pytest-dev#2981

Remove logger parameter from catching_logs

Fix memory leak caused by fixture values never been garbage collected

Fixes pytest-dev#3038