build(deps): bump chardet from 4.0.0 to 5.1.0 in /docs

[dependabot]

Bumps chardet from 4.0.0 to 5.1.0.

Release notes

Sourced from chardet's releases.

chardet 5.1.0

Features

• Add should_rename_legacy argument to most functions, which will rename older encodings to their more modern equivalents (e.g., GB2312 becomes GB18030) (#264, @​dan-blanchard)
• Add capital letter sharp S and ISO-8859-15 support (#222, @​SimonWaldherr)
• Add a prober for MacRoman encoding (#5 updated as c292b52a97e57c95429ef559af36845019b88b33, Rob Speer and @​dan-blanchard )
• Add --minimal flag to chardetect command (#214, @​dan-blanchard)
• Add type annotations to the project and run mypy on CI (#261, @​jdufresne)
• Add support for Python 3.11 (#274, @​hugovk)

Fixes

• Clarify LGPL version in License trove classifier (#255, @​musicinmybrain)
• Remove support for EOL Python 3.6 (#260, @​jdufresne)
• Remove unnecessary guards for non-falsey values (#259, @​jdufresne)

Misc changes

• Switch to Python 3.10 release in GitHub actions (#257, @​jdufresne)
• Remove setup.py in favor of build package (#262, @​jdufresne)
• Run tests on macos, Windows, and 3.11-dev (#267, @​dan-blanchard)

chardet 5.0.0

⚠️ This release is the first release of chardet that no longer supports Python < 3.6 ⚠️

In addition to that change, it features the following user-facing changes:

• Added a prober for Johab Korean (#207, @​grizlupo)
• Added a prober for UTF-16/32 BE/LE (#109, #206, @​jpz)
• Added test data for Croatian, Czech, Hungarian, Polish, Slovak, Slovene, Greek, and Turkish, which should help prevent future errors with those languages
• Improved XML tag filtering, which should improve accuracy for XML files (#208)
• Tweaked SingleByteCharSetProber confidence to match latest uchardet (#209)
• Made detect_all return child prober confidences (#210)
• Updated examples in docs (#223, @​domdfcoding)
• Documentation fixes (#212, #224, #225, #226, #220, #221, #244 from too many to mention)
• Minor performance improvements (#252, @​deedy5)
• Add support for Python 3.10 when testing (#232, @​jdufresne)
• Lots of little development cycle improvements, mostly thanks to @​jdufresne

Commits

• 8087f00 Bump version to 5.1.0
• 041875f Revert "Distinguish between final and intermediate ResultDict (#266)"
• 7264282 Add support for Python 3.11 (#274)
• ac934fe Ignore black reformatting for blame
• fa4c1af Fix mypy error
• 99cd852 Update black pre-commit
• 0a0aa94 Fix linter
• c6f8e7d Stop running jobs twice on PRs
• 85035f5 Make sure we have test dependencies when linting
• 5b5e841 Add should_rename_legacy flag
• Additional commits viewable in compare view

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 commands and options

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)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}