chore(deps): bump sqlalchemy from 2.0.31 to 2.0.32 (#207)

Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.31
to 2.0.32.
<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.32</h1>
<p>Released: August 5, 2024</p>
<h2>general</h2>
<ul>
<li>
<p><strong>[general] [bug] [regression]</strong> Restored legacy class
names removed from
<code>sqlalalchemy.orm.collections.*</code>, including
<code>_orm.MappedCollection</code>,
<code>_orm.mapped_collection()</code>,
<code>_orm.column_mapped_collection()</code>,
<code>_orm.attribute_mapped_collection()</code>. Pull request courtesy
Takashi
Kajinami.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11435">#11435</a></p>
</li>
</ul>
<h2>orm</h2>
<ul>
<li>
<p><strong>[orm] [usecase]</strong> The <code>_orm.aliased.name</code>
parameter to <code>_orm.aliased()</code> may now
be combined with the <code>_orm.aliased.flat</code> parameter, producing
per-table names based on a name-prefixed naming convention. Pull request
courtesy Eric Atkin.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11575">#11575</a></p>
</li>
<li>
<p><strong>[orm] [bug] [regression]</strong> Fixed regression going back
to 1.4 where accessing a collection using the
&quot;dynamic&quot; strategy on a transient object and attempting to
query would
raise an internal error rather than the expected
<code>NoResultFound</code>
that occurred in 1.3.</p>
<p>This change is also <strong>backported</strong> to: 1.4.53</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11562">#11562</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Fixed issue where using the
<code>_orm.Query.enable_eagerloads()</code> and
<code>_orm.Query.yield_per()</code> methods at the same time, in order
to disable
eager loading that's configured on the mapper directly, would be
silently
ignored, leading to errors or unexpected eager population of
attributes.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/10834">#10834</a></p>
</li>
<li>
<p><strong>[orm] [bug] [regression]</strong> Fixed regression appearing
in 2.0.21 caused by <a
href="https://www.sqlalchemy.org/trac/ticket/10279">#10279</a> where
using
a <code>_sql.delete()</code> or <code>_sql.update()</code> against an
ORM class that is
the base of an inheritance hierarchy, while also specifying that
subclasses
should be loaded polymorphically, would leak the polymorphic joins into
the
UPDATE or DELETE statement as well creating incorrect SQL.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11625">#11625</a></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.31&new-version=2.0.32)](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>

pyproject.toml

@@ -9,7 +9,7 @@ packages = [{ include = "regtech_user_fi_management", from = "src" }]
 [tool.poetry.dependencies]
 python = ">=3.12,<4"
 python-dotenv = "^1.0.0"
-SQLAlchemy = "^2.0.31"
+SQLAlchemy = "^2.0.32"
 psycopg2-binary = "^2.9.6"
 asyncpg = "^0.29.0"
 alembic = "^1.13.2"