chore(deps-dev): update pytest-django requirement from >=4.5.0 to >=4.12.0 (#655)

[//]: # (dependabot-start)
⚠️  **Dependabot is rebasing this PR** ⚠️ 

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

[//]: # (dependabot-end)

Updates the requirements on [pytest-django](https://github.com/pytest-dev/pytest-django) to permit the latest version.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/pytest-dev/pytest-django/blob/main/docs/changelog.rst">pytest-django's changelog</a>.</em></p>
<blockquote>
<h2>v4.12.0 (2026-02-14)</h2>
<p>Compatibility
^^^^^^^^^^^^^</p>
<ul>
<li>Official Python 3.14 support.</li>
<li>Dropped support for Python 3.9, minimum version is now Python 3.10.</li>
<li>Official Django 6.0 support.</li>
</ul>
<p>Improvements
^^^^^^^^^^^^</p>
<ul>
<li>The :ref:<code>multiple databases &lt;multi-db&gt;</code> support added in v4.3.0 is no longer considered experimental.</li>
<li>Added :func:<code>@pytest.mark.django_isolate_apps &lt;pytest.mark.django_isolate_apps&gt;</code>
for isolating Django's app registry in pytest tests, and a
:fixture:<code>django_isolated_apps</code> fixture to access the isolated Apps registry instance if needed.</li>
</ul>
<h2>v4.11.1 (2025-04-03)</h2>
<p>Bugfixes
^^^^^^^^</p>
<ul>
<li>Fixed a regression in v4.11.0 for Django <code>TestCase</code> tests using the <code>databases</code> class variable (<code>[#1188](pytest-dev/pytest-django#1188) &lt;https://github.com/pytest-dev/pytest-django/issues/1188&gt;</code>__).</li>
</ul>
<h2>v4.11.0 (2025-04-01)</h2>
<p>Compatibility
^^^^^^^^^^^^^</p>
<ul>
<li>Added official support for Django 5.2 (<code>PR [#1179](pytest-dev/pytest-django#1179) &lt;https://github.com/pytest-dev/pytest-django/pull/1179&gt;</code>__).</li>
<li>Dropped testing on MySQL’s MyISAM storage engine (<code>PR [#1180](pytest-dev/pytest-django#1180) &lt;https://github.com/pytest-dev/pytest-django/pull/1180&gt;</code>__).</li>
</ul>
<p>Bugfixes
^^^^^^^^</p>
<ul>
<li>
<p>Stopped setting up and serializing databases on test session setup when not needed (the database is not requested / <code>serialized_rollback</code> is not used).
On test databases with large amounts of pre-seeded data, this may remove a delay of a few seconds when running <code>pytest --reuse-db</code>.</p>
<p>The determination of which databases to setup is done by static inspection of the test suite.
Using pytest's dynamic features to request db access, such as :meth:<code>request.getfixturevalue(&quot;db&quot;) &lt;pytest.FixtureRequest.getfixturevalue&gt;</code>, may throw off this analysis.
If you start seeing <code>DatabaseOperationForbidden</code> or &quot;unable to open database&quot; errors, this is likely the cause.
To fix this, decorate at least one test with the :func:<code>django_db &lt;pytest.mark.django_db&gt;</code> marker with appropriate <code>databases</code> and <code>serialized_rollback</code> settings.</p>
</li>
</ul>
<h2>v4.10.0 (2025-02-10)</h2>
<p>Compatibility</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/pytest-dev/pytest-django/commit/a2a94956cc24bb30030510710f0f27e61efb0cf0"><code>a2a9495</code></a> Release 4.12.0</li>
<li><a href="https://github.com/pytest-dev/pytest-django/commit/020bc237ac7be78ab3a2780d07637f77166a6263"><code>020bc23</code></a> tests: make sure access to default can also be blocked</li>
<li><a href="https://github.com/pytest-dev/pytest-django/commit/bcefbe832468f764b0f2665548aae8a9f75820a7"><code>bcefbe8</code></a> Add support for isolating apps in tests</li>
<li><a href="https://github.com/pytest-dev/pytest-django/commit/39c8dcc249d5c103d29d170a5ad63a2fe7067049"><code>39c8dcc</code></a> plugin: add a note why we reorder tests</li>
<li><a href="https://github.com/pytest-dev/pytest-django/commit/1830acd6193ad6d851131c9ed805c003c10ce27a"><code>1830acd</code></a> pyproject.toml: require pytest 9 for self tests, switch to native toml config...</li>
<li><a href="https://github.com/pytest-dev/pytest-django/commit/f19da084b9b8b131c5ae178f1a8a907ec6e3567b"><code>f19da08</code></a> Fix the order of the test cases that use the live_server fixture</li>
<li><a href="https://github.com/pytest-dev/pytest-django/commit/92858eed573ce1786d0f67d242426c7f8f75dd7b"><code>92858ee</code></a> docs: add pytest 9.0+ native TOML configuration format</li>
<li><a href="https://github.com/pytest-dev/pytest-django/commit/3f550d93947acda430c27be578b7619c25abddc8"><code>3f550d9</code></a> build(deps): bump hynek/build-and-inspect-python-package</li>
<li><a href="https://github.com/pytest-dev/pytest-django/commit/1f50dd29b8778e645ca7a88a285b30a9c788afc4"><code>1f50dd2</code></a> Drop obsolete traces of Django 5.0 in CI</li>
<li><a href="https://github.com/pytest-dev/pytest-django/commit/247ec1c365da3d25f230dde22b7a0e1805749d09"><code>247ec1c</code></a> Fix <code>PytestCollectionWarning</code> for <code>TestRunner</code> class (<a href="https://redirect.github.com/pytest-dev/pytest-django/issues/1259">#1259</a>)</li>
<li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest-django/compare/v4.5.0...v4.12.0">compare view</a></li>
</ul>
</details>
<br />

[gtmq-generated]

Gtmq-generated: true

Author: dependabot[bot]

pyproject.toml

@@ -25,7 +25,7 @@ dependencies = [
 dev = [
     "netifaces>=0.11.0",
     "pytest>=7.4.0",
-    "pytest-django>=4.5.0",
+    "pytest-django>=4.12.0",
     "pytest-cov>=4.1.0",
     "pytest-asyncio>=0.21.0",
     "flake8>=7.3.0",