Update pytest-asyncio to 0.22.0

[pyup-bot]

This PR updates pytest-asyncio from 0.20.3 to 0.22.0.

Changelog

0.22.0

* Class-scoped and module-scoped event loops can be requested
via the _asyncio_event_loop_ mark. [620](https://github.com/pytest-dev/pytest-asyncio/pull/620)
* Deprecate redefinition of the _event_loop_ fixture. [587](https://github.com/pytest-dev/pytest-asyncio/issues/531)
Users requiring a class-scoped or module-scoped asyncio event loop for their tests
should mark the corresponding class or module with _asyncio_event_loop_.
* Test items based on asynchronous generators always exit with _xfail_ status and emit a warning during the collection phase. This behavior is consistent with synchronous yield tests. [642](https://github.com/pytest-dev/pytest-asyncio/issues/642)
* Remove support for Python 3.7
* Declare support for Python 3.12

0.21.1

* Output a proper error message when an invalid `asyncio_mode` is selected.
* Extend warning message about unclosed event loops with additional possible cause.
531 
* Previously, some tests reported "skipped" or "xfailed" as a result. Now all tests report a "success" result.

0.21.0

* Drop compatibility with pytest 6.1. Pytest-asyncio now depends on pytest 7.0 or newer.
* pytest-asyncio cleans up any stale event loops when setting up and tearing down the
event_loop fixture. This behavior has been deprecated and pytest-asyncio emits a
DeprecationWarning when tearing down the event_loop fixture and current event loop
has not been closed.

Links

• PyPI: https://pypi.org/project/pytest-asyncio
• Changelog: https://data.safetycli.com/changelogs/pytest-asyncio/
• Repo: https://github.com/pytest-dev/pytest-asyncio

[pyup-bot]

Closing this in favor of #525