chore(deps): bump sqlalchemy from 2.0.35 to 2.0.36 (#241)

Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.35
to 2.0.36.
<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.36</h1>
<p>Released: October 15, 2024</p>
<h2>orm</h2>
<ul>
<li>
<p><strong>[orm] [usecase]</strong> Added new parameter
<code>_orm.mapped_column.hash</code> to ORM constructs
such as <code>_orm.mapped_column()</code>,
<code>_orm.relationship()</code>, etc.,
which is interpreted for ORM Native Dataclasses in the same way as other
dataclass-specific field parameters.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11923">#11923</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Fixed bug in ORM bulk update/delete
where using RETURNING with bulk
update/delete in combination with <code>populate_existing</code> would
fail to
accommodate the <code>populate_existing</code> option.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11912">#11912</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Continuing from <a
href="https://www.sqlalchemy.org/trac/ticket/11912">#11912</a>, columns
marked with
<code>mapped_column.onupdate</code>,
<code>mapped_column.server_onupdate</code>, or <code>Computed</code> are
now
refreshed in ORM instances when running an ORM enabled UPDATE with WHERE
criteria, even if the statement does not use RETURNING or
<code>populate_existing</code>.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11917">#11917</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Fixed regression caused by fixes to
joined eager loading in <a
href="https://www.sqlalchemy.org/trac/ticket/11449">#11449</a>
released in 2.0.31, where a particular joinedload case could not be
asserted correctly. We now have an example of that case so the assertion
has been repaired to allow for it.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11965">#11965</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Improved the error message emitted when
trying to map as dataclass a class
while also manually providing the <code>__table__</code> attribute.
This usage is currently not supported.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/11973">#11973</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Refined the check which the ORM lazy
loader uses to detect &quot;this would be
loading by primary key and the primary key is NULL, skip loading&quot;
to take
into account the current setting for the
<code>orm.Mapper.allow_partial_pks</code> parameter. If this parameter
is
<code>False</code>, then a composite PK value that has partial NULL
elements should
also be skipped. This can apply to some composite overlapping foreign
key
configurations.</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.35&new-version=2.0.36)](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.35", extras = ["asyncio"]}
+SQLAlchemy = { version = "^2.0.36", extras = ["asyncio"]}
 psycopg2-binary = "^2.9.10"
 asyncpg = "^0.30.0"
 alembic = "^1.14.0"