chore(deps-py): bump pytest from 8.4.2 to 9.0.0 (#142)

Bumps [pytest](https://github.com/pytest-dev/pytest) from 8.4.2 to
9.0.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pytest-dev/pytest/releases">pytest's
releases</a>.</em></p>
<blockquote>
<h2>9.0.0</h2>
<h1>pytest 9.0.0 (2025-11-05)</h1>
<h2>New features</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/1367">#1367</a>:
<strong>Support for subtests</strong> has been added.</p>
<p><code>subtests &lt;subtests&gt;</code> are an alternative to
parametrization, useful in situations where the parametrization values
are not all known at collection time.</p>
<p>Example:</p>
<pre lang="python"><code>def contains_docstring(p: Path) -&gt; bool:
&quot;&quot;&quot;Return True if the given Python file contains a
top-level docstring.&quot;&quot;&quot;
    ...
<p>def test_py_files_contain_docstring(subtests: pytest.Subtests) -&gt;
None:
for path in Path.cwd().glob(&quot;*.py&quot;):
with subtests.test(path=str(path)):
assert contains_docstring(path)
</code></pre></p>
<p>Each assert failure or error is caught by the context manager and
reported individually, giving a clear picture of all files that are
missing a docstring.</p>
<p>In addition, <code>unittest.TestCase.subTest</code> is now also
supported.</p>
<p>This feature was originally implemented as a separate plugin in <a
href="https://github.com/pytest-dev/pytest-subtests">pytest-subtests</a>,
but since then has been merged into the core.</p>
<blockquote>
<p>[!NOTE]
This feature is experimental and will likely evolve in future releases.
By that we mean that we might change how subtests are reported on
failure, but the functionality and how to use it are stable.</p>
</blockquote>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/13743">#13743</a>:
Added support for <strong>native TOML configuration files</strong>.</p>
<p>While pytest, since version 6, supports configuration in
<code>pyproject.toml</code> files under
<code>[tool.pytest.ini_options]</code>,
it does so in an &quot;INI compatibility mode&quot;, where all
configuration values are treated as strings or list of strings.
Now, pytest supports the native TOML data model.</p>
<p>In <code>pyproject.toml</code>, the native TOML configuration is
under the <code>[tool.pytest]</code> table.</p>
<pre lang="toml"><code># pyproject.toml
[tool.pytest]
minversion = &quot;9.0&quot;
addopts = [&quot;-ra&quot;, &quot;-q&quot;]
testpaths = [
    &quot;tests&quot;,
    &quot;integration&quot;,
]
</code></pre>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/pytest-dev/pytest/commit/f4b0fd2294a0b2f89bf308d513d574e1e2e01ad5"><code>f4b0fd2</code></a>
Prepare release version 9.0.0</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/52d8e6812667880b523d285b95c53af73b7866e3"><code>52d8e68</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/13889">#13889</a>
from bluetech/regendoc-restore</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/d6d3e4a4760bcdc9c2078b015d5967937b1df602"><code>d6d3e4a</code></a>
doc: fixes for regendoc</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/7cb397413f3d8270fad4de1004039d45cb1a841d"><code>7cb3974</code></a>
doc: restore missing &quot;# content of pytest.toml&quot; regendoc
commands</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/5ae9e4761b42a7c84d53486733d6ea8567dedccb"><code>5ae9e47</code></a>
build(deps): Bump django in /testing/plugins_integration (<a
href="https://redirect.github.com/pytest-dev/pytest/issues/13881">#13881</a>)</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/adb3658f091b8f3c4e0948298b1aefd16b6ce372"><code>adb3658</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/13864">#13864</a>
from bluetech/config-cleanups-2</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/a28c08efc6af57b94875c517dee0da0d9c201d7e"><code>a28c08e</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/13875">#13875</a>
from bluetech/ci-tweaks</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/a250954723eda5ae2cb60396a516762b08fa0644"><code>a250954</code></a>
ci: split publish-to-pypi and push-tag jobs</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/ebc152f84e40796ae88fadb71e4fd95c2946bfc3"><code>ebc152f</code></a>
ci: update setup python's from 3.11 or 3.* to 3.13</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/dfd796fb2ff6356af116f76d307f853dc11a10b2"><code>dfd796f</code></a>
ci: move running update-plugin-list script to tox</li>
<li>Additional commits viewable in <a
href="https://github.com/pytest-dev/pytest/compare/8.4.2...9.0.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pytest&package-manager=uv&previous-version=8.4.2&new-version=9.0.0)](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>
Co-authored-by: cqc-melf <[email protected]>

Author: dependabot[bot]