Bump pytest-asyncio from 0.23.4 to 0.23.5 (#96)

Bumps [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio)
from 0.23.4 to 0.23.5.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pytest-dev/pytest-asyncio/releases">pytest-asyncio's
releases</a>.</em></p>
<blockquote>
<h2>pytest-asyncio 0.23.5</h2>
<h1>0.23.5 (2024-02-09)</h1>
<ul>
<li>Declare compatibility with pytest 8 <a
href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/737">#737</a></li>
<li>Fix typing errors with recent versions of mypy <a
href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/769">#769</a></li>
<li>Prevent DeprecationWarning about internal use of
<code>asyncio.get_event_loop()</code> from affecting test cases <a
href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/757">#757</a></li>
</ul>
<h2>Known issues</h2>
<p>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 <a
href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/706">#706</a>).
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.</p>
<h2>pytest-asyncio 0.23.5a0</h2>
<h1>0.23.5 (UNRELEASED)</h1>
<ul>
<li>Declare compatibility with pytest 8 <a
href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/737">#737</a></li>
<li>Fix typing errors with recent versions of mypy <a
href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/769">#769</a></li>
</ul>
<h2>Known issues</h2>
<p>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 <a
href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/706">#706</a>).
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.</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/pytest-dev/pytest-asyncio/commit/3aef60532f2a1c634af5f4539eabdd4fbfffcabc"><code>3aef605</code></a>
[build] Update actions/upload-artifact and actions/download-artifact to
v4.</li>
<li><a
href="https://github.com/pytest-dev/pytest-asyncio/commit/4b1908d9ed26895c194a4bb8d4c61cef2dfc5067"><code>4b1908d</code></a>
[fix] Prevent DeprecationWarning from bubbling to user code.</li>
<li><a
href="https://github.com/pytest-dev/pytest-asyncio/commit/fc6d6cfeb2fd7db1572869b80517ec436ef95e7f"><code>fc6d6cf</code></a>
Fix typing and update to mypy 1.8.0 (<a
href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/769">#769</a>)</li>
<li><a
href="https://github.com/pytest-dev/pytest-asyncio/commit/6008cf16e2a5c6c365e249db975a8a1afec3c8bf"><code>6008cf1</code></a>
Build(deps): Bump pluggy from 1.3.0 to 1.4.0 in
/dependencies/default</li>
<li><a
href="https://github.com/pytest-dev/pytest-asyncio/commit/712c51bde9d385ecf69ee98e8c40fa6868b80a75"><code>712c51b</code></a>
Build(deps): Bump coverage from 7.4.0 to 7.4.1 in
/dependencies/default</li>
<li><a
href="https://github.com/pytest-dev/pytest-asyncio/commit/42fd3041c3e44e3428adee10afa7935757375ff9"><code>42fd304</code></a>
Build(deps): Bump hypothesis in /dependencies/default</li>
<li><a
href="https://github.com/pytest-dev/pytest-asyncio/commit/a40b4f662454e3b33d44fc552958439db167a294"><code>a40b4f6</code></a>
Build(deps): Bump urllib3 from 2.1.0 to 2.2.0 in /dependencies/docs</li>
<li><a
href="https://github.com/pytest-dev/pytest-asyncio/commit/9d90f8ec6e68e2564f5116cf2accfe0b202af390"><code>9d90f8e</code></a>
Build(deps): Bump certifi in /dependencies/docs</li>
<li><a
href="https://github.com/pytest-dev/pytest-asyncio/commit/fe5da0771dcc0b939ae9ee3d1b9a50cfc4860667"><code>fe5da07</code></a>
Build(deps): Bump markupsafe from 2.1.4 to 2.1.5 in
/dependencies/docs</li>
<li><a
href="https://github.com/pytest-dev/pytest-asyncio/commit/42b140decf8de145e76dcd61894a7963b10e815b"><code>42b140d</code></a>
fix compatibility with pytest ^8 (<a
href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/776">#776</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/pytest-dev/pytest-asyncio/compare/v0.23.4...v0.23.5">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pytest-asyncio&package-manager=pip&previous-version=0.23.4&new-version=0.23.5)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>