build(deps-dev): bump pytest from 8.2.2 to 8.3.2 (#171)

Bumps [pytest](https://github.com/pytest-dev/pytest) from 8.2.2 to
8.3.2.
<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>8.3.2</h2>
<h1>pytest 8.3.2 (2024-07-24)</h1>
<h2>Bug fixes</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12652">#12652</a>:
Resolve regression [conda]{.title-ref} environments where no longer
being automatically detected.</p>
<p>-- by <code>RonnyPfannschmidt</code>{.interpreted-text
role=&quot;user&quot;}</p>
</li>
</ul>
<h2>8.3.1</h2>
<h1>pytest 8.3.1 (2024-07-20)</h1>
<p>The 8.3.0 release failed to include the change notes and docs for the
release. This patch release remedies this. There are no other
changes.</p>
<h2>8.3.0</h2>
<h1>pytest 8.3.0 (2024-07-20)</h1>
<h2>New features</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12231">#12231</a>:
Added [--xfail-tb]{.title-ref} flag, which turns on traceback output for
XFAIL results.</p>
<ul>
<li>If the [--xfail-tb]{.title-ref} flag is not given, tracebacks for
XFAIL results are NOT shown.</li>
<li>The style of traceback for XFAIL is set with [--tb]{.title-ref}, and
can be [auto|long|short|line|native|no]{.title-ref}.</li>
<li>Note: Even if you have [--xfail-tb]{.title-ref} set, you won't see
them if [--tb=no]{.title-ref}.</li>
</ul>
<p>Some history:</p>
<p>With pytest 8.0, [-rx]{.title-ref} or [-ra]{.title-ref} would not
only turn on summary reports for xfail, but also report the tracebacks
for xfail results. This caused issues with some projects that utilize
xfail, but don't want to see all of the xfail tracebacks.</p>
<p>This change detaches xfail tracebacks from [-rx]{.title-ref}, and now
we turn on xfail tracebacks with [--xfail-tb]{.title-ref}. With this,
the default [-rx]{.title-ref}/ [-ra]{.title-ref} behavior is identical
to pre-8.0 with respect to xfail tracebacks. While this is a behavior
change, it brings default behavior back to pre-8.0.0 behavior, which
ultimately was considered the better course of action.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12281">#12281</a>:
Added support for keyword matching in marker expressions.</p>
<p>Now tests can be selected by marker keyword arguments.
Supported values are <code>int</code>{.interpreted-text
role=&quot;class&quot;}, (unescaped) <code>str</code>{.interpreted-text
role=&quot;class&quot;}, <code>bool</code>{.interpreted-text
role=&quot;class&quot;} &amp; <code>None</code>{.interpreted-text
role=&quot;data&quot;}.</p>
<p>See <code>marker examples
&lt;marker_keyword_expression_example&gt;</code>{.interpreted-text
role=&quot;ref&quot;} for more information.</p>
<p>-- by <code>lovetheguitar</code>{.interpreted-text
role=&quot;user&quot;}</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12567">#12567</a>:
Added <code>--no-fold-skipped</code> command line option.</p>
<p>If this option is set, then skipped tests in short summary are no
longer grouped
by reason but all tests are printed individually with their nodeid in
the same
way as other statuses.</p>
<p>-- by <code>pbrezina</code>{.interpreted-text
role=&quot;user&quot;}</p>
</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/bbcec9c46509c417ef58e4849847b4aa43f4591e"><code>bbcec9c</code></a>
Prepare release version 8.3.2</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/78fe8b61fa716cd9775f1e37b395bab7679734a6"><code>78fe8b6</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12657">#12657</a>
from pytest-dev/patchback/backports/8.3.x/6c806b499...</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/238bad2d2a1f1dbb47d740c84b5b4f5224f8a965"><code>238bad2</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12656">#12656</a>
from RonnyPfannschmidt/fix-12652-detect-conda-env</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/ae6034a781a50b572fa700911e5d8e0eb074ca17"><code>ae6034a</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12641">#12641</a>
from pytest-dev/patchback/backports/8.3.x/c03989cee...</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/31337aba02a7698a87a6792eacf887fceff08af2"><code>31337ab</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12640">#12640</a>
from pytest-dev/update-user</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/ca3070b1356e5edf43f085d8c4ec1b34627061dd"><code>ca3070b</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12637">#12637</a>
from pytest-dev/release-8.3.1</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/de98446075cc07c768387cf64ba497dd75c205de"><code>de98446</code></a>
Prepare release version 8.3.1</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/bd0a0424037825bc23b9bf299115e92c53a67a9c"><code>bd0a042</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12636">#12636</a>
from pytest-dev/update-release-notes</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/664325bc9fd90217f51fe7cc0e9fff2f29a41a15"><code>664325b</code></a>
doc/changelog: update 8.3.0 notes</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/19d225d0ab0f586a9a1fc878dff871495c12bd06"><code>19d225d</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12635">#12635</a>
from pytest-dev/release-8.3.0</li>
<li>Additional commits viewable in <a
href="https://github.com/pytest-dev/pytest/compare/8.2.2...8.3.2">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pytest&package-manager=pip&previous-version=8.2.2&new-version=8.3.2)](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>