⬆️ Bump greenlet from 1.1.3.post0 to 2.0.1 (#117)

Bumps [greenlet](https://github.com/python-greenlet/greenlet) from
1.1.3.post0 to 2.0.1.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/python-greenlet/greenlet/blob/master/CHANGES.rst">greenlet's
changelog</a>.</em></p>
<blockquote>
<h1>2.0.1 (2022-11-07)</h1>
<ul>
<li>Python 3.11: Fix a memory leak. See <code>issue 328
&lt;https://github.com/python-greenlet/greenlet/issues/328&gt;</code>_
and
<code>gevent issue 1924
&lt;https://github.com/gevent/gevent/issues/1924&gt;</code>_.</li>
</ul>
<h1>2.0.0.post0 (2022-11-03)</h1>
<ul>
<li>Add <code>Programming Language :: Python :: 3.11</code> to the PyPI
classifier metadata.</li>
</ul>
<h1>2.0.0 (2022-10-31)</h1>
<ul>
<li>Nothing changed yet.</li>
</ul>
<h1>2.0.0rc5 (2022-10-31)</h1>
<ul>
<li>Linux: Fix another group of rare crashes that could occur when
shutting down an
interpeter running multiple threads. See <code>issue 325
&lt;https://github.com/python-greenlet/greenlet/issues/325&gt;</code>_.</li>
</ul>
<h1>2.0.0rc4 (2022-10-30)</h1>
<ul>
<li>Linux: Fix a rare crash that could occur when shutting down an
interpreter running multiple threads, when some of those threads are
in greenlets making calls to functions that release the GIL.</li>
</ul>
<h1>2.0.0rc3 (2022-10-29)</h1>
<ul>
<li>Python 2: Fix a crash that could occur when raising an old-style
instance object.</li>
</ul>
<h1>2.0.0rc2 (2022-10-28)</h1>
<ul>
<li>Workaround <code>a CPython 3.8 bug
&lt;https://github.com/python/cpython/issues/81308&gt;</code>_ that
could cause
the interpreter to crash during an early phase of shutdown with the
message &quot;Fatal Python error: Python memory allocator called
without</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/python-greenlet/greenlet/commit/69f6483c41776fb9095c3fd7b02d3e4ede289c78"><code>69f6483</code></a>
Preparing release 2.0.1</li>
<li><a
href="https://github.com/python-greenlet/greenlet/commit/df2154d45b8cfa751de1fc9e6a95e0b09a53becf"><code>df2154d</code></a>
Merge pull request <a
href="https://github-redirect.dependabot.com/python-greenlet/greenlet/issues/329">#329</a>
from python-greenlet/issue328</li>
<li><a
href="https://github.com/python-greenlet/greenlet/commit/aa6f2515b2fefced69be933952bd1f3319d0de58"><code>aa6f251</code></a>
Python 3.11: Fix a memory leak switching to greenlets.</li>
<li><a
href="https://github.com/python-greenlet/greenlet/commit/7389976dc748677dd4fce535b91ef07e4387c1d6"><code>7389976</code></a>
Back to development: 2.0.1</li>
<li><a
href="https://github.com/python-greenlet/greenlet/commit/0216c2ae008cb185292b136e34ba92ae3f40da6b"><code>0216c2a</code></a>
Preparing release 2.0.0.post0</li>
<li><a
href="https://github.com/python-greenlet/greenlet/commit/7e1704ccbf2ade357416b63d95d645120df1f4dc"><code>7e1704c</code></a>
.github/workflows/tests.yml: Move to final release of 3.11</li>
<li><a
href="https://github.com/python-greenlet/greenlet/commit/f18bff43df80c5190760dc2aedfa436a1fae7bed"><code>f18bff4</code></a>
setup.py: Add Python 3.11 to the PyPI classifier metadata.</li>
<li><a
href="https://github.com/python-greenlet/greenlet/commit/fc50ac173d0011492c19c87eb619017fdab47fd9"><code>fc50ac1</code></a>
Back to development: 2.0.1</li>
<li><a
href="https://github.com/python-greenlet/greenlet/commit/f9c29d90b1fd33e3ade1272f46e17dfe17d651e6"><code>f9c29d9</code></a>
Preparing release 2.0.0</li>
<li><a
href="https://github.com/python-greenlet/greenlet/commit/4ba1df63dcd40c8056f21117a91bf56d0be8a6eb"><code>4ba1df6</code></a>
Back to development: 2.0.0rc6</li>
<li>Additional commits viewable in <a
href="https://github.com/python-greenlet/greenlet/compare/1.1.3.post0...2.0.1">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=greenlet&package-manager=pip&previous-version=1.1.3.post0&new-version=2.0.1)](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 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>

requirements.txt

@@ -69,7 +69,7 @@ fastjsonschema==2.16.2
     # via nbformat
 filelock==3.8.0
     # via virtualenv
-greenlet==1.1.3.post0
+greenlet==2.0.1
     # via sqlalchemy
 identify==2.5.8
     # via pre-commit