chore: Bump the runtime-dependencies group with 2 updates (#521)

Bumps the runtime-dependencies group with 2 updates:
[psycopg](https://github.com/psycopg/psycopg) and
[sqlalchemy](https://github.com/sqlalchemy/sqlalchemy).

Updates `psycopg` from 3.2.5 to 3.2.6
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/psycopg/psycopg/blob/master/docs/news.rst">psycopg's
changelog</a>.</em></p>
<blockquote>
<p>.. currentmodule:: psycopg</p>
<p>.. index::
single: Release notes
single: News</p>
<h1><code>psycopg</code> release notes</h1>
<h2>Future releases</h2>
<p>Python 3.3.0 (unreleased)
^^^^^^^^^^^^^^^^^^^^^^^^^</p>
<ul>
<li>Drop support for Python 3.8.</li>
</ul>
<h2>Current release</h2>
<p>Python 3.2.6
^^^^^^^^^^^^</p>
<ul>
<li>Fix connection semantic when using
<code>target_session_attrs=prefer-standby</code>

(:ticket:<code>[#1021](https://github.com/psycopg/psycopg/issues/1021)</code>).</li>
</ul>
<p>Psycopg 3.2.5
^^^^^^^^^^^^^</p>
<ul>
<li>3x faster UUID loading thanks to C implementation
(:tickets:<code>[#447](psycopg/psycopg#447),
[#998](https://github.com/psycopg/psycopg/issues/998)</code>).</li>
</ul>
<p>Psycopg 3.2.4
^^^^^^^^^^^^^</p>
<ul>
<li>Don't lose notifies received whilst the
<code>~Connection.notifies()</code> iterator
is not running
(:ticket:<code>[#962](https://github.com/psycopg/psycopg/issues/962)</code>).</li>
<li>Make sure that the notifies callback is called during the use of the
<code>~Connection.notifies()</code> generator
(:ticket:<code>[#972](https://github.com/psycopg/psycopg/issues/972)</code>).</li>
<li>Raise the correct error returned by the database (such as
<code>!AdminShutdown</code>
or <code>!IdleInTransactionSessionTimeout</code>) instead of a generic
<code>OperationalError</code> when a server error causes a client
disconnection

(:ticket:<code>[#988](https://github.com/psycopg/psycopg/issues/988)</code>).</li>
<li>Build macOS dependencies from sources instead using the Homebrew
versions
in order to avoid problems with <code>MACOSX_DEPLOYMENT_TARGET</code>
(:ticket:<code>[#858](https://github.com/psycopg/psycopg/issues/858)</code>).</li>
<li>Bump libpq to 17.2 in Linux and macOS binary packages.</li>
<li>Bump libpq to 16.4 in Windows binary packages, using the <code>vcpkg
library</code>__

(:ticket:<code>[#966](https://github.com/psycopg/psycopg/issues/966)</code>).</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/psycopg/psycopg/commit/dfc113613c067600355a14c2e4010d03cbef51bd"><code>dfc1136</code></a>
chore: bump psycopg package version to 3.2.6</li>
<li><a
href="https://github.com/psycopg/psycopg/commit/a75e03f8f4cf3a882c6017e4935f86d1e5069d11"><code>a75e03f</code></a>
Merge branch 'fix-target_session_attrs-prefer-standby' into
maint-3.2</li>
<li><a
href="https://github.com/psycopg/psycopg/commit/1377bb66a4cbd6343738567de646ce96ac177902"><code>1377bb6</code></a>
test: skip target_session_attrs with libpw &lt; 14</li>
<li><a
href="https://github.com/psycopg/psycopg/commit/b37dc1a35b8c24707bc844f8cc8ee965121ba25b"><code>b37dc1a</code></a>
fix: implement libpq semantic for
target_session_attrs=prefer-standby</li>
<li><a
href="https://github.com/psycopg/psycopg/commit/c946e403678ef1370bcb3c2f71ecd66badee5ff9"><code>c946e40</code></a>
fix win32 libpq missing error</li>
<li><a
href="https://github.com/psycopg/psycopg/commit/4645f33eddc05fb03a4d97e7593fcc520ebd303d"><code>4645f33</code></a>
chore: bump psycopg package version to 3.2.6.dev1</li>
<li>See full diff in <a
href="https://github.com/psycopg/psycopg/compare/3.2.5...3.2.6">compare
view</a></li>
</ul>
</details>
<br />

Updates `sqlalchemy` from 2.0.38 to 2.0.39
<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.39</h1>
<p>Released: March 11, 2025</p>
<h2>orm</h2>
<ul>
<li>
<p><strong>[orm] [bug]</strong> Fixed bug where using DML returning such
as <code>Insert.returning()</code> with
an ORM model that has <code>_orm.column_property()</code> constructs
that contain
subqueries would fail with an internal error.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/12326">#12326</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Fixed bug in ORM enabled UPDATE (and
theoretically DELETE) where using a
multi-table DML statement would not allow ORM mapped columns from
mappers
other than the primary UPDATE mapper to be named in the RETURNING
clause;
they would be omitted instead and cause a column not found
exception.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/12328">#12328</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Fixed issue where the &quot;is ORM&quot;
flag of a <code>select()</code> or other ORM
statement would not be propagated to the ORM <code>Session</code> based
on a
multi-part operator expression alone, e.g. such as <code>Cls.attr +
Cls.attr + Cls.attr</code> or similar, leading to ORM behaviors not
taking place for such
statements.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/12357">#12357</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Fixed issue where using
<code>_orm.aliased()</code> around a <code>CTE</code>
construct could cause inappropriate &quot;duplicate CTE&quot; errors in
cases where
that aliased construct appeared multiple times in a single
statement.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/12364">#12364</a></p>
</li>
</ul>
<h2>sql</h2>
<ul>
<li>
<p><strong>[sql] [bug]</strong> Added new parameters
<code>AddConstraint.isolate_from_table</code> and
<code>DropConstraint.isolate_from_table</code>, defaulting to True,
which
both document and allow to be controllable the long-standing behavior of
these two constructs blocking the given constraint from being included
inline within the &quot;CREATE TABLE&quot; sequence, under the
assumption that
separate add/drop directives were to be used.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/12382">#12382</a></p>
</li>
</ul>
<h2>typing</h2>
<ul>
<li><strong>[typing] [usecase]</strong> Support generic types for
compound selects (<code>_sql.union()</code>,</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 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 <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Author: dependabot[bot]