Bump flit from 3.9.0 to 3.10.0 (#37)

Summary:
Bumps [flit](https://github.com/pypa/flit) from 3.9.0 to 3.10.0.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/pypa/flit/blob/main/doc/history.rst">flit's changelog</a>.</em></p>
<blockquote>
<h1>Release history</h1>
<h2>Version 3.10</h2>
<ul>
<li><code>flit publish</code> can now use PyPI tokens stored in keyring (:ghpull:<code>649</code>),
either project tokens with a 'username' like
:samp:<code>pypi_token:project:{project_name}</code> (use the <code>normalised form of the name &lt;https://packaging.python.org/en/latest/specifications/name-normalization/&gt;</code>_)
or user tokens (:samp:<code>pypi_token:user:{username}</code>).</li>
<li>The <code>--python</code> option can now take the path of a virtualenv folder, as an
alternative to a Python executable (:ghpull:<code>667</code>).</li>
<li>Flit will work with current development versions of Pythona again (:ghpull:<code>684</code>).</li>
<li>The <code>flit</code> command line package now requires Python 3.8 or above (:ghpulL:<code>660</code>).
<code>flit_core</code> still works with Python 3.6 or above.</li>
<li>The metadata in packages now has the names of optional dependency groups
(&quot;extras&quot;) normalised, complying with version 2.3 of the metadata standard
(:ghpull:<code>676</code>, :ghpull:<code>697</code>).</li>
<li>The <code>flit</code> command line package now depends on pip (:ghpull:<code>647</code>).</li>
<li>Fix potential substitution of environment variables into passwords read from
<code>.pypirc</code> files (:ghpull:<code>652</code>).</li>
<li>A warning is now shown when building packages which specify the old
<code>flit.buildapi</code> backend, which should be replaced by <code>flit_core.buildapi</code>
(:ghpull:<code>674</code>). It's a good idea to always set a maximum version for the
build requirement, to protect against changes in future major versions of Flit.</li>
<li>Avoid using the deprecated <code>datetime.utcfromtimestamp()</code> (:ghpull:<code>682</code>).</li>
<li>Flit now has a <code>SECURITY.md</code> file in the Github repository (:ghpull:<code>665</code>).</li>
<li>The tests for <code>flit_core</code> are no longer part of the installed package,
reducing the size of the wheels (:ghpull:<code>691</code>).</li>
</ul>
<h2>Version 3.9</h2>
<ul>
<li>New options :option:<code>flit build --use-vcs</code> and :option:<code>flit build --no-use-vcs</code>
to enable &amp; disable including all committed files in the sdist. For now
<code>--use-vcs</code> is the default, but this is likely to change in a future
version, to bring <code>flit build</code> in line with standard build frontends like
<code>python -m build</code> (:ghpull:<code>625</code>).</li>
<li>Sdist file names, and the name of the top-level folder in an sdist, are now
normalised, in accordance with :pep:<code>625</code> (:ghpull:<code>628</code>).</li>
<li>A statically defined version number can now be parsed from files called
<code>version.py</code>, <code>_version.py</code> or <code>__version__.py</code> inside a package, as well
as from <code>__init__.py</code>, so executing code is required in fewer cases
(:ghpull:<code>630</code>).</li>
<li>Fix setting the flag for regular files in zip metadata (:ghpull:<code>639</code>).</li>
<li>The timestamp embedded in the gzip wrapper for sdists now defaults to a fixed
date, so building an sdist twice on the same machine should produce identical
results, even without any special steps (:ghpull:<code>635</code>). Setting
:envvar:<code>SOURCE_DATE_EPOCH</code> is still recommended for properly</li>
</ul>

</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/pypa/flit/commit/80666776e9051120e41778f15d90c1bb6c7363bc"><code>8066677</code></a> Merge pull request <a href="https://redirect.github.com/pypa/flit/issues/700">#700</a> from pypa/win-py3.13-tests</li>
<li><a href="https://github.com/pypa/flit/commit/34445e96d4a19318aef24e0d3a677bd045a7498c"><code>34445e9</code></a> Better test for absolute Python exe path on Windows</li>
<li><a href="https://github.com/pypa/flit/commit/d340f1c38a026d186176546421e85af5a2822562"><code>d340f1c</code></a> Fix checks for absolute paths in config on Python 3.13 &amp; Windows</li>
<li><a href="https://github.com/pypa/flit/commit/c57b10113bff7cbc8c8cb5ecf793fc933b881030"><code>c57b101</code></a> Ensure CI also runs on tag pushes</li>
<li><a href="https://github.com/pypa/flit/commit/5c416e532af745fb505f50d5cd278a5a1a95a794"><code>5c416e5</code></a> Simpler way to ensure dependencies are installed in CI</li>
<li><a href="https://github.com/pypa/flit/commit/74ab93b0db73f7e30e0a029f83591cdfa71e2107"><code>74ab93b</code></a> Extend CI to Python 3.13</li>
<li><a href="https://github.com/pypa/flit/commit/ba39a3f0d6916d293a4df5dbcb458df7b2d1b9d4"><code>ba39a3f</code></a> Building Flit may require a not-yet-released version of flit_core; build with...</li>
<li><a href="https://github.com/pypa/flit/commit/1195f41fb9a25e7dab1499271bbedbb6c74ef566"><code>1195f41</code></a> Bump version: 3.9.0 → 3.10.0</li>
<li><a href="https://github.com/pypa/flit/commit/29cf6619bc7f79bc7cf846ae78d925910d5996c4"><code>29cf661</code></a> Merge pull request <a href="https://redirect.github.com/pypa/flit/issues/695">#695</a> from pypa/changelog-3.10</li>
<li><a href="https://github.com/pypa/flit/commit/e99f7606558d6792d262082453791b8fdfc505dc"><code>e99f760</code></a> Mention extra name normalisation in changelog</li>
<li>Additional commits viewable in <a href="https://github.com/pypa/flit/compare/3.9.0...3.10.0">compare view</a></li>
</ul>
</details>
<br />

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

Pull Request resolved: #37

Reviewed By: bowiechen

Differential Revision: D65355733

Pulled By: itamaro

fbshipit-source-id: 2a840fcba41d8766e3dcb05347aeafa96f41b8fa

pyproject.toml

@@ -33,7 +33,7 @@ dependencies = [
 dev = [
     "async-timeout==4.0.3",
     "coverage==7.6.4",
-    "flit==3.9.0",
+    "flit==3.10.0",
 ]
 
 [project.urls]