Build(deps): Bump typing-extensions from 4.11.0 to 4.12.0 (#1119)

Bumps [typing-extensions](https://github.com/python/typing_extensions)
from 4.11.0 to 4.12.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/python/typing_extensions/releases">typing-extensions's
releases</a>.</em></p>
<blockquote>
<h2>4.12.0</h2>
<p>This release focuses on compatibility with the upcoming release of
Python 3.13. Most changes are related to the implementation of type
parameter defaults (PEP 696).</p>
<p>Thanks to all of the people who contributed patches, especially Alex
Waygood, who did most of the work adapting typing-extensions to the
CPython PEP 696 implementation.</p>
<p>There is a single change since 4.12.0rc1:</p>
<ul>
<li>Fix incorrect behaviour of <code>typing_extensions.ParamSpec</code>
on Python 3.8 and
3.9 that meant that
<code>isinstance(typing_extensions.ParamSpec(&quot;P&quot;),
typing.TypeVar)</code> would have a
different result in some situations depending on whether or not a
profiling
function had been set using <code>sys.setprofile</code>. Patch by Alex
Waygood.</li>
</ul>
<p>Changes included in 4.12.0rc1:</p>
<ul>
<li>Improve the implementation of type parameter defaults (PEP 696)
<ul>
<li>Backport the <code>typing.NoDefault</code> sentinel object from
Python 3.13.
TypeVars, ParamSpecs and TypeVarTuples without default values now have
their <code>__default__</code> attribute set to this sentinel
value.</li>
<li>TypeVars, ParamSpecs and TypeVarTuples now have a
<code>has_default()</code>
method, matching <code>typing.TypeVar</code>,
<code>typing.ParamSpec</code> and
<code>typing.TypeVarTuple</code> on Python 3.13+.</li>
<li>TypeVars, ParamSpecs and TypeVarTuples with
<code>default=None</code> passed to
their constructors now have their <code>__default__</code> attribute set
to <code>None</code>
at runtime rather than <code>types.NoneType</code>.</li>
<li>Fix most tests for <code>TypeVar</code>, <code>ParamSpec</code> and
<code>TypeVarTuple</code> on Python
3.13.0b1 and newer.</li>
<li>Backport CPython PR <a
href="https://redirect.github.com/python/cpython/pull/118774">#118774</a>,
allowing type parameters without default values to follow those with
default values in some type parameter lists. Patch by Alex Waygood,
backporting a CPython PR by Jelle Zijlstra.</li>
<li>It is now disallowed to use a <code>TypeVar</code> with a default
value after a
<code>TypeVarTuple</code> in a type parameter list. This matches the
CPython
implementation of PEP 696 on Python 3.13+.</li>
<li>Fix bug in PEP-696 implementation where a default value for a
<code>ParamSpec</code>
would be cast to a tuple if a list was provided.
Patch by Alex Waygood.</li>
</ul>
</li>
<li>Fix <code>Protocol</code> tests on Python 3.13.0a6 and newer.
3.13.0a6 adds a new
<code>__static_attributes__</code> attribute to all classes in Python,
which broke some assumptions made by the implementation of
<code>typing_extensions.Protocol</code>. Similarly, 3.13.0b1 adds the
new
<code>__firstlineno__</code> attribute to all classes.</li>
<li>Fix <code>AttributeError</code> when using
<code>typing_extensions.runtime_checkable</code>
in combination with <code>typing.Protocol</code> on Python 3.12.2 or
newer.
Patch by Alex Waygood.</li>
<li>At runtime, <code>assert_never</code> now includes the repr of the
argument</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/python/typing_extensions/blob/main/CHANGELOG.md">typing-extensions's
changelog</a>.</em></p>
<blockquote>
<h1>Release 4.12.0 (May 23, 2024)</h1>
<p>This release is mostly the same as 4.12.0rc1 but fixes one more
longstanding bug.</p>
<ul>
<li>Fix incorrect behaviour of <code>typing_extensions.ParamSpec</code>
on Python 3.8 and
3.9 that meant that
<code>isinstance(typing_extensions.ParamSpec(&quot;P&quot;),
typing.TypeVar)</code> would have a
different result in some situations depending on whether or not a
profiling
function had been set using <code>sys.setprofile</code>. Patch by Alex
Waygood.</li>
</ul>
<h1>Release 4.12.0rc1 (May 16, 2024)</h1>
<p>This release focuses on compatibility with the upcoming release of
Python 3.13. Most changes are related to the implementation of type
parameter defaults (PEP 696).</p>
<p>Thanks to all of the people who contributed patches, especially Alex
Waygood, who did most of the work adapting typing-extensions to the
CPython PEP 696 implementation.</p>
<p>Full changelog:</p>
<ul>
<li>Improve the implementation of type parameter defaults (PEP 696)
<ul>
<li>Backport the <code>typing.NoDefault</code> sentinel object from
Python 3.13.
TypeVars, ParamSpecs and TypeVarTuples without default values now have
their <code>__default__</code> attribute set to this sentinel
value.</li>
<li>TypeVars, ParamSpecs and TypeVarTuples now have a
<code>has_default()</code>
method, matching <code>typing.TypeVar</code>,
<code>typing.ParamSpec</code> and
<code>typing.TypeVarTuple</code> on Python 3.13+.</li>
<li>TypeVars, ParamSpecs and TypeVarTuples with
<code>default=None</code> passed to
their constructors now have their <code>__default__</code> attribute set
to <code>None</code>
at runtime rather than <code>types.NoneType</code>.</li>
<li>Fix most tests for <code>TypeVar</code>, <code>ParamSpec</code> and
<code>TypeVarTuple</code> on Python
3.13.0b1 and newer.</li>
<li>Backport CPython PR <a
href="https://redirect.github.com/python/cpython/pull/118774">#118774</a>,
allowing type parameters without default values to follow those with
default values in some type parameter lists. Patch by Alex Waygood,
backporting a CPython PR by Jelle Zijlstra.</li>
<li>It is now disallowed to use a <code>TypeVar</code> with a default
value after a
<code>TypeVarTuple</code> in a type parameter list. This matches the
CPython
implementation of PEP 696 on Python 3.13+.</li>
<li>Fix bug in PEP-696 implementation where a default value for a
<code>ParamSpec</code>
would be cast to a tuple if a list was provided.
Patch by Alex Waygood.</li>
</ul>
</li>
<li>Fix <code>Protocol</code> tests on Python 3.13.0a6 and newer.
3.13.0a6 adds a new
<code>__static_attributes__</code> attribute to all classes in Python,
which broke some assumptions made by the implementation of
<code>typing_extensions.Protocol</code>. Similarly, 3.13.0b1 adds the
new
<code>__firstlineno__</code> attribute to all classes.</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/python/typing_extensions/commit/f90a8dc40b60bf43510b8611a07d8cc570544ffe"><code>f90a8dc</code></a>
Prepare release 4.12.0 (<a
href="https://redirect.github.com/python/typing_extensions/issues/408">#408</a>)</li>
<li><a
href="https://github.com/python/typing_extensions/commit/118e1a604a857d54cb70a2a1f930b425676d6cb4"><code>118e1a6</code></a>
Make sure <code>isinstance(typing_extensions.ParamSpec(&quot;P&quot;),
typing.TypeVar)</code> is u...</li>
<li><a
href="https://github.com/python/typing_extensions/commit/910141ab8295b422851f83ffc46c9eb04bbca719"><code>910141a</code></a>
Add security documentation (<a
href="https://redirect.github.com/python/typing_extensions/issues/403">#403</a>)</li>
<li><a
href="https://github.com/python/typing_extensions/commit/0dbc7c971f7ec61f12a1466f8d8f222bdf9a4b31"><code>0dbc7c9</code></a>
Prepare release 4.12.0rc1 (<a
href="https://redirect.github.com/python/typing_extensions/issues/402">#402</a>)</li>
<li><a
href="https://github.com/python/typing_extensions/commit/1da5d3d24441cc059fe4d49131588b719ee41d59"><code>1da5d3d</code></a>
Update actions/setup-python (<a
href="https://redirect.github.com/python/typing_extensions/issues/401">#401</a>)</li>
<li><a
href="https://github.com/python/typing_extensions/commit/72298f05fc520f05ca9a280f5ed0fa3e5de27041"><code>72298f0</code></a>
4.12.0a2 (<a
href="https://redirect.github.com/python/typing_extensions/issues/400">#400</a>)</li>
<li><a
href="https://github.com/python/typing_extensions/commit/465ba786ca98b99e75905fe2aaa98131ef27d54c"><code>465ba78</code></a>
Fix publish workflow (<a
href="https://redirect.github.com/python/typing_extensions/issues/399">#399</a>)</li>
<li><a
href="https://github.com/python/typing_extensions/commit/21fde1f0d04f78e080ca4f6119293b607d9a0475"><code>21fde1f</code></a>
Prepare releaes 4.12.0a1 (<a
href="https://redirect.github.com/python/typing_extensions/issues/398">#398</a>)</li>
<li><a
href="https://github.com/python/typing_extensions/commit/63d827754489f307630dea2e0f58dfab65837a66"><code>63d8277</code></a>
Add workflow for Trusted Publishing (<a
href="https://redirect.github.com/python/typing_extensions/issues/395">#395</a>)</li>
<li><a
href="https://github.com/python/typing_extensions/commit/074d053727f8c658e65dc9a3ccd9760421de52a9"><code>074d053</code></a>
Backport PEP-696 specialisation on Python &gt;=3.11.1 (<a
href="https://redirect.github.com/python/typing_extensions/issues/397">#397</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/python/typing_extensions/compare/4.11.0...4.12.0">compare
view</a></li>
</ul>
</details>
<br />

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