Use aiohttp middleware for mocking

[sarayourfriend]

Description

Fixes #166
Replaces #167 cc @cjw296

This solves a host of issues, including #166, as well as that middlewares would not have previously worked.

This aiohttp feature is documented here: https://docs.aiohttp.org/en/stable/client_advanced.html#client-middleware

This PR changes the aiohttp implementation to be middleware based by refactoring the interceptor to implement aiohttp's ClientMiddlewareType (as the __call__ method). Rather than mocking all of aiohttp's _request method, now pook injects its interceptor as the final middleware, then defers to the real _request method.

aiohttp's _request method picks up the middleware. As it is last, it will be the "innermost" middleware, and can intercept the actual request mechanism.

Because this still prevents aiohttp's _connect_and_send_request from running when a mock matches, and thus prevents the Connector.connect method from running, this won't fully solve other issues like #152. Some traces will start to work now, though.

PR Checklist

• I've added tests for any code changes
  • The existing test suite should all pass without modification, and they do!
  • I've also copied over @cjw296's aiohttp-specific basic auth test from WIP - aiohttp: support for auth from ClientSession #167 to confirm that this change does fix aiohttp mocking does not match on basic auth headers provided in ClientSession #166.
• I've documented any new features

[sarayourfriend]

This check isn't necessary, or even accurate. The underlying HTTPHeaderDict class's extend method handles a host of different types of inputs and should be the source of any relevant TypeErrors anyway.

[cjw296]

Awesome, thanks! I ran out of steam on this a while back, as you saw... Do you know when you'll be able to get this out into a release I'd be able to use?

[sarayourfriend]

Yep! Released here in v2.1.5: https://github.com/h2non/pook/releases/tag/v2.1.5

Already on PyPI as well 🙂