chore(deps): bump sqlalchemy from 2.0.34 to 2.0.35 (#229)

Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.34
to 2.0.35.
<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.35</h1>
<p>Released: September 16, 2024</p>
<h2>orm</h2>
<ul>
<li>
<p><strong>[orm] [bug] [typing]</strong> Fixed issue where it was not
possible to use <code>typing.Literal</code> with
<code>Mapped[]</code> on Python 3.8 and 3.9. Pull request courtesy
Frazer McLean.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11820">#11820</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Fixed issue in ORM evaluator where two
datatypes being evaluated with the
SQL concatenator operator would not be checked for
<code>UnevaluatableError</code> based on their datatype; this missed the
case
of <code>_postgresql.JSONB</code> values being used in a concatenate
operation
which is supported by PostgreSQL as well as how SQLAlchemy renders the
SQL
for this operation, but does not work at the Python level. By
implementing
<code>UnevaluatableError</code> for this combination, ORM update
statements
will now fall back to &quot;expire&quot; when a concatenated JSON value
used in a SET
clause is to be synchronized to a Python object.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11849">#11849</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> An warning is emitted if
<code>_orm.joinedload()</code> or
<code>_orm.subqueryload()</code> are used as a top level option against
a
statement that is not a SELECT statement, such as with an
<code>insert().returning()</code>. There are no JOINs in INSERT
statements nor is
there a &quot;subquery&quot; that can be repurposed for subquery eager
loading, and
for UPDATE/DELETE joinedload does not support these either, so it is
never
appropriate for this use to pass silently.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11853">#11853</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Fixed issue where using loader options
such as <code>_orm.selectinload()</code>
with additional criteria in combination with ORM DML such as
<code>_sql.insert()</code> with RETURNING would not correctly set up
internal
contexts required for caching to work correctly, leading to incorrect
results.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11855">#11855</a></p>
</li>
</ul>
<h2>mysql</h2>
<ul>
<li><strong>[mysql] [bug]</strong> Fixed issue in mariadbconnector
dialect where query string arguments that
weren't checked integer or boolean arguments would be ignored, such as
string arguments like <code>unix_socket</code>, etc. As part of this
change, the
argument parsing for particular elements such as
<code>client_flags</code>,
<code>compress</code>, <code>local_infile</code> has been made more
consistent across all</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.34&new-version=2.0.35)](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 = { version = "^2.0.34", extras = ["asyncio"]}
+SQLAlchemy = { version = "^2.0.35", extras = ["asyncio"]}
 psycopg2-binary = "^2.9.6"
 asyncpg = "^0.29.0"
 alembic = "^1.13.2"