Bump sqlalchemy from 2.0.21 to 2.0.22 (#134)

Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 2.0.21
to 2.0.22.
<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.22</h1>
<p>Released: October 12, 2023</p>
<h2>orm</h2>
<ul>
<li>
<p><strong>[orm] [usecase]</strong> Added method
<code>_orm.Session.get_one()</code> that behaves like
<code>_orm.Session.get()</code> but raises an exception instead of
returning
<code>None</code> if no instance was found with the provided primary
key.
Pull request courtesy of Carlos Sousa.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/10202">#10202</a></p>
</li>
<li>
<p><strong>[orm] [usecase]</strong> Added an option to permanently close
sessions.
Set to <code>False</code> the new parameter
<code>_orm.Session.close_resets_only</code>
will prevent a <code>_orm.Session</code> from performing any other
operation after <code>_orm.Session.close()</code> has been called.</p>
<p>Added new method <code>_orm.Session.reset()</code> that will reset a
<code>_orm.Session</code>
to its initial state. This is an alias of
<code>_orm.Session.close()</code>,
unless <code>_orm.Session.close_resets_only</code> is set to
<code>False</code>.</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/7787">#7787</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Fixed a wide range of
<code>_orm.mapped_column()</code> parameters that were not
being transferred when using the <code>_orm.mapped_column()</code>
object inside
of a pep-593 <code>Annotated</code> object, including
<code>_orm.mapped_column.sort_order</code>,
<code>_orm.mapped_column.deferred</code>,
<code>_orm.mapped_column.autoincrement</code>,
<code>_orm.mapped_column.system</code>,
<code>_orm.mapped_column.info</code>
etc.</p>
<p>Additionally, it remains not supported to have dataclass arguments,
such as
<code>_orm.mapped_column.kw_only</code>,
<code>_orm.mapped_column.default_factory</code> etc. indicated within
the
<code>_orm.mapped_column()</code> received by <code>Annotated</code>, as
this is not
supported with pep-681 Dataclass Transforms. A warning is now emitted
when
these parameters are used within <code>Annotated</code> in this way (and
they
continue to be ignored).</p>
<p>References: <a
href="https://www.sqlalchemy.org/trac/ticket/10046">#10046</a>, <a
href="https://www.sqlalchemy.org/trac/ticket/10369">#10369</a></p>
</li>
<li>
<p><strong>[orm] [bug]</strong> Fixed issue where calling
<code>_engine.Result.unique()</code> with a new-style
<code>select()</code> query in the ORM, where one or more columns yields
values
that are of &quot;unknown hashability&quot;, typically when using JSON
functions like
<code>func.json_build_object()</code> without providing a type, would
fail
internally when the returned values were not actually hashable. The
behavior is repaired to test the objects as they are received for</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.21&new-version=2.0.22)](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>

Pipfile

@@ -39,7 +39,7 @@ pytz = "==2023.3"
 s3transfer = "==0.4.2"
 sendgrid = "==6.10.0"
 six = "==1.16.0"
-sqlalchemy = "==2.0.21"
+sqlalchemy = "==2.0.22"
 starkbank-ecdsa = "==2.2.0"
 tatsu = "==5.8.3"
 urllib3 = "==1.26.18"