Update dependency pytest-asyncio to v0.23.7 (#442)

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [pytest-asyncio](https://togithub.com/pytest-dev/pytest-asyncio)
([changelog](https://pytest-asyncio.readthedocs.io/en/latest/reference/changelog.html))
| `==0.23.6` -> `==0.23.7` |
[![age](https://developer.mend.io/api/mc/badges/age/pypi/pytest-asyncio/0.23.7?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/pypi/pytest-asyncio/0.23.7?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/pypi/pytest-asyncio/0.23.6/0.23.7?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pytest-asyncio/0.23.6/0.23.7?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>pytest-dev/pytest-asyncio (pytest-asyncio)</summary>

###
[`v0.23.7`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.7):
pytest-asyncio 0.23.7

[Compare
Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.6...v0.23.7)

### 0.23.7 (2024-05-19)

- Silence deprecation warnings about unclosed event loops that occurred
with certain CPython patch releases
[#&#8203;817](https://togithub.com/pytest-dev/pytest-asyncio/pull/817)

#### Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item
of the test suite (i.e. session, packages, modules, classes, functions)
and allows tests to be run in those loops when marked accordingly.
Pytest-asyncio currently assumes that async fixture scope is correlated
with the new event loop scope. This prevents fixtures from being
evaluated independently from the event loop scope and breaks some
existing test suites (see
[#&#8203;706](https://togithub.com/pytest-dev/pytest-asyncio/issues/706)).
For example, a test suite may require all fixtures and tests to run in
the same event loop, but have async fixtures that are set up and torn
down for each module. If you're affected by this issue, please continue
using the v0.21 release, until it is resolved.

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/allenporter/pyrainbird).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zNjguMTAiLCJ1cGRhdGVkSW5WZXIiOiIzNy4zNjguMTAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

requirements_dev.txt

@@ -17,7 +17,7 @@ mitmproxy==10.3.0
 parameterized==0.9.0
 mashumaro==3.13
 pytest-aiohttp==1.0.5
-pytest-asyncio==0.23.6
+pytest-asyncio==0.23.7
 pytest-golden==0.2.2
 python-dateutil==2.9.0.post0
 requests==2.31.0