chore(deps): update dependency charset-normalizer to v3.4.9

[projecttickbot]

This MR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
charset-normalizer (changelog)	==3.4.7 → ==3.4.9

---

Release Notes

jawah/charset_normalizer (charset-normalizer)

v3.4.9

Compare Source

Fixed

• Regression in our fallback path leading to a decode error. (#​771)
  We've yanked 3.4.8 as a result of that bug.

v3.4.8

Compare Source

Fixed

• Wall import time due to cascade codec imports for our multibyte first sort of iana supported codecs (#​742)
• Unnecessary json import at runtime (#​753)
• Inverse capitalization not seen by noise detector (#​731)

Changed

• No longer holding a global cache for our noise / coherence measurements. Relax RSS memory usage.
• Micro-optimizations in our noise / coherence measurements.
• No longer using regex search by default for our preemptive charset mark algorithm.
• Raised upperbound of setuptools to v83.
• Raised upperbound of mypy(c) to v2.1.

Removed

• Redundant UTF7 BOM marker (#​730)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Mend Renovate.

[projecttickbot]

🚧 Test build queued — waiting for capacity.

[projecttickbot]

✅ Danger review

All Danger checks passed.

⚠️ Warnings

• dbfbfe5: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines.
• This merge request does not have any assignee yet. Setting an assignee clarifies who needs to take action on the merge request at any given time.
• This merge request does not refer to an existing milestone.
• Please add a category label to this merge request so Foreman can route section/stage/group labels.
• Please add a changelog commit trailer to at least one commit. If a changelog entry is not needed, add any of the ~"documentation" labels.

We advise getting a review from GitLab Duo Code. You can assign @GitLabDuo as a reviewer to this merge request.

Reviewer roulette

Changes that require review have been detected! A merge request is normally
reviewed by both a reviewer and a maintainer in its primary category and by a
maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each
review slot. Feel free to
override these selections
if you think someone else would be better-suited
or use the GitLab Review Workload Dashboard
to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the
Engineering workflow
and code review guidelines.
Please consider assigning a reviewer or maintainer who is a
domain expert
in the area of the merge request.

Reviewer	Maintainer
No reviewer available	No maintainer available

Once you've decided who will review this merge request, mention them as you
normally would! Danger does not automatically notify them for you.

If needed, you can retry the 🔁 danger-review job that generated this comment.