chore: bump email-validator from 2.1.0.post1 to 2.3.0 (#178)

Bumps
[email-validator](https://github.com/JoshData/python-email-validator)
from 2.1.0.post1 to 2.3.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/JoshData/python-email-validator/releases">email-validator's
releases</a>.</em></p>
<blockquote>
<h2>v2.3.0</h2>
<ul>
<li>The package name is changed from using an underscore
(email_validator) to a dash (email-validator) to match PyPi's normalized
package name.</li>
<li>The library no longer checks that the local part is at most 64
characters because a more careful reading of RFC 5321 indicates the
limit is optional and such email addresses have been found in the wild.
However the check can be restored using a new <code>strict=True</code>
parameter, and the overall 254 character email address length limit is
still in place.</li>
<li>New EmailSyntaxError messages are used for some exiting syntax
errors related to @-sign homoglyphs and invalid characters in
internationalized domains.</li>
<li>When using <code>allow_display_name=True</code>, display names are
now returned with Unicode NFC normalization.</li>
<li>TypeError is now raised if something other than str (or bytes) is
passed as the email address.</li>
</ul>
<h2>2.2.0 (June 20, 2024)</h2>
<ul>
<li>Email addresses with internationalized local parts could, with rare
Unicode characters, be returned as valid but actually be invalid in
their normalized form (returned in the <code>normalized</code> field).
Local parts now re-validated after Unicode NFC normalization to ensure
that invalid characters cannot be injected into the normalized address
and that characters with length-increasing NFC normalizations cannot
cause a local part to exceed the maximum length after
normalization.</li>
<li>The length check for email addresses with internationalized local
parts is now also applied to the original address string prior to
Unicode NFC normalization, which may be longer and could exceed the
maximum email address length, to protect callers who do not use the
returned normalized address.</li>
<li>Improved error message for IDNA domains that are too long or have
invalid characters after Unicode normalization.</li>
<li>A new option to parse <code>My Name &lt;address@domain&gt;</code>
strings, i.e. a display name plus an email address in angle brackets, is
now available. It is off by default.</li>
<li>Improvements to Python typing.</li>
<li>Some additional tests added.</li>
</ul>
<h2>v2.1.2</h2>
<h2>2.1.2 (June 16, 2024)</h2>
<ul>
<li>The domain name length limit is corrected from 255 to 253 IDNA ASCII
characters. I misread the RFCs.</li>
<li>When a domain name has no MX record but does have an A or AAAA
record, if none of the IP addresses in the response are globally
reachable (i.e. not Private-Use, Loopback, etc.), the response is
treated as if there was no A/AAAA response and the email address will
fail the deliverability check.</li>
<li>When a domain name has no MX record but does have an A or AAAA
record, the mx field in the object returned by validate_email
incorrectly held the IP addresses rather than the domain itself.</li>
<li>Fixes in tests.</li>
</ul>
<h2>v2.1.1 (February 26, 2024)</h2>
<ul>
<li>Fixed typo 'marking' instead of 'marketing' in case-insensitive
mailbox name list.</li>
<li>When DNS-based deliverability checks fail, in some cases exceptions
are now thrown with <code>raise ... from</code> for better nested
exception tracking.</li>
<li>Fixed tests to work when no local resolver can be configured.</li>
<li>This project is now licensed under the Unlicense (instead of
CC0).</li>
<li>Minor improvements to tests.</li>
<li>Minor improvements to code style.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/JoshData/python-email-validator/blob/main/CHANGELOG.md">email-validator's
changelog</a>.</em></p>
<blockquote>
<h2>2.3.0 (August 26, 2025)</h2>
<ul>
<li>The package name is changed from using an underscore
(email_validator) to a dash (email-validator) to match PyPi's normalized
package name.</li>
<li>The library no longer checks that the local part is at most 64
characters because a more careful reading of RFC 5321 indicates the
limit is optional and such email addresses have been found in the wild.
However the check can be restored using a new <code>strict=True</code>
parameter, and the overall 254 character email address length limit is
still in place.</li>
<li>New EmailSyntaxError messages are used for some exiting syntax
errors related to @-sign homoglyphs and invalid characters in
internationalized domains.</li>
<li>When using <code>allow_display_name=True</code>, display names are
now returned with Unicode NFC normalization.</li>
<li>TypeError is now raised if something other than str (or bytes) is
passed as the email address.</li>
</ul>
<h2>2.2.0 (June 20, 2024)</h2>
<ul>
<li>Email addresses with internationalized local parts could, with rare
Unicode characters, be returned as valid but actually be invalid in
their normalized form (returned in the <code>normalized</code> field).
In particular, it is possible to get a normalized address with a
&quot;;&quot; character, which is not valid and could change the
interpretation of the address. Local parts now re-validated after
Unicode NFC normalization to ensure that invalid characters cannot be
injected into the normalized address and that characters with
length-increasing NFC normalizations cannot cause a local part to exceed
the maximum length after normalization. Thanks to <a
href="mailto:khanh@calif.io">khanh@calif.io</a> from <a
href="https://calif.io">https://calif.io</a> for reporting the
issue.</li>
<li>The length check for email addresses with internationalized local
parts is now also applied to the original address string prior to
Unicode NFC normalization, which may be longer and could exceed the
maximum email address length, to protect callers who do not use the
returned normalized address.</li>
<li>Improved error message for IDNA domains that are too long or have
invalid characters after Unicode normalization.</li>
<li>A new option to parse <code>My Name &lt;address@domain&gt;</code>
strings, i.e. a display name plus an email address in angle brackets, is
now available. It is off by default.</li>
<li>Improvements to Python typing.</li>
<li>Some additional tests added.</li>
</ul>
<h2>2.1.2 (June 16, 2024)</h2>
<ul>
<li>The domain name length limit is corrected from 255 to 253 IDNA ASCII
characters. I misread the RFCs.</li>
<li>When a domain name has no MX record but does have an A or AAAA
record, if none of the IP addresses in the response are globally
reachable (i.e. not Private-Use, Loopback, etc.), the response is
treated as if there was no A/AAAA response and the email address will
fail the deliverability check.</li>
<li>When a domain name has no MX record but does have an A or AAAA
record, the mx field in the object returned by validate_email
incorrectly held the IP addresses rather than the domain itself.</li>
<li>Fixes in tests.</li>
</ul>
<h2>2.1.1 (February 26, 2024)</h2>
<ul>
<li>Fixed typo 'marking' instead of 'marketing' in case-insensitive
mailbox name list.</li>
<li>When DNS-based deliverability checks fail, in some cases exceptions
are now thrown with <code>raise ... from</code> for better nested
exception tracking.</li>
<li>Fixed tests to work when no local resolver can be configured.</li>
<li>This project is now licensed under the Unlicense (instead of
CC0).</li>
<li>Minor improvements to tests.</li>
<li>Minor improvements to code style.</li>
</ul>
<h2>2.1.0 (October 22, 2023)</h2>
<ul>
<li>Python 3.8+ is now required (support for Python 3.7 was
dropped).</li>
<li>The old <code>email</code> field on the returned
<code>ValidatedEmail</code> object, which in the previous version was
superseded by <code>normalized</code>, will now raise a deprecation
warning if used. See <a
href="https://stackoverflow.com/q/879173">https://stackoverflow.com/q/879173</a>
for strategies to suppress the DeprecationWarning.</li>
<li>A <code>__version__</code> module attribute is added.</li>
<li>The email address argument to validate_email is now marked as
positional-only to better reflect the documented usage using the new
Python 3.8 feature.</li>
</ul>
<h2>2.0.0 (April 15, 2023)</h2>
<p>This is a major update to the library, but since email address specs
haven't changed there should be no significant changes to which email
addresses are considered valid or invalid with default options. There
are new options for accepting unusual email addresses that were
previously always rejected, some changes to how DNS errors are handled,
many changes in error message text, and major internal improvements
including the addition of type annotations. Python 3.7+ is now required.
Details follow:</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/JoshData/python-email-validator/commits/v2.3.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=email-validator&package-manager=pip&previous-version=2.1.0.post1&new-version=2.3.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 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>

backend/requirements.txt

@@ -25,7 +25,7 @@ boto3==1.29.7
 botocore==1.32.7
 
 # Email
-email-validator==2.1.0.post1
+email-validator==2.3.0
 emails==0.6.0
 jinja2==3.1.2