Build: Bump sqlalchemy from 2.0.39 to 2.0.40 (#1874)

Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.39
to 2.0.40.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/sqlalchemy/sqlalchemy/releases">sqlalchemy's
releases</a>.</em></p>
<blockquote>
<h1>2.0.40</h1>
<p>Released: March 27, 2025</p>
<h2>orm</h2>
<ul>
<li>
<p><strong>[orm] [bug]</strong> Fixed regression which occurred as of
2.0.37 where the checked
<code>ArgumentError</code> that's raised when an inappropriate type or
object
is used inside of a <code>Mapped</code> annotation would raise
<code>TypeError</code>
with &quot;boolean value of this clause is not defined&quot; if the
object resolved
into a SQL expression in a boolean context, for programs where future
annotations mode was not enabled. This case is now handled explicitly
and
a new error message has also been tailored for this case. In addition,
as
there are at least half a dozen distinct error scenarios for
intepretation
of the <code>Mapped</code> construct, these scenarios have all been
unified
under a new subclass of <code>ArgumentError</code> called
<code>MappedAnnotationError</code>, to provide some continuity between
these
different scenarios, even though specific messaging remains
distinct.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/12329">#12329</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Fixed regression in ORM Annotated
Declarative class interpretation caused
by <code>typing_extension==4.13.0</code> that introduced a different
implementation
for <code>TypeAliasType</code> while SQLAlchemy assumed that it would be
equivalent
to the <code>typing</code> version, leading to pep-695 type annotations
not
resolving to SQL types as expected.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/12473">#12473</a></p>
</li>
</ul>
<h2>sql</h2>
<ul>
<li>
<p><strong>[sql] [usecase]</strong> Implemented support for the GROUPS
frame specification in window functions
by adding <code>_sql.over.groups</code> option to
<code>_sql.over()</code>
and <code>FunctionElement.over()</code>. Pull request courtesy Kaan
Dikmen.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/12450">#12450</a></p>
</li>
<li>
<p><strong>[sql] [bug]</strong> Fixed issue in <code>CTE</code>
constructs involving multiple DDL
<code>_sql.Insert</code> statements with multiple VALUES parameter sets
where the
bound parameter names generated for these parameter sets would conflict,
generating a compile time error.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/12363">#12363</a></p>
</li>
<li>
<p><strong>[sql] [bug]</strong> Fixed regression caused by <a
href="https://www.sqlalchemy.org/trac/ticket/7471">#7471</a> leading to
a SQL compilation
issue where name disambiguation for two same-named FROM clauses with
table
aliasing in use at the same time would produce invalid SQL in the FROM
clause with two &quot;AS&quot; clauses for the aliased table, due to
double aliasing.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/sqlalchemy/sqlalchemy/commits">compare
view</a></li>
</ul>
</details>
<br />


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

Author: dependabot[bot]