Bump crate-ci/typos from 1.16.5 to 1.16.9

[dependabot]

Bumps crate-ci/typos from 1.16.5 to 1.16.9.

Release notes

Sourced from crate-ci/typos's releases.

v1.16.9

[1.16.9] - 2023-08-30

Fixes

• Start correcting arguement again

v1.16.8

[1.16.8] - 2023-08-21

Fixes

• (action) With fetch-depth:0, don't ignore excludes and fail with spaces in file names

v1.16.7

[1.16.7] - 2023-08-21

Fixes

• Provide more context for IO error messages

v1.16.6

[1.16.6] - 2023-08-18

Fixes

• Provide more context for IO error messages

Changelog

Sourced from crate-ci/typos's changelog.

[1.16.9] - 2023-08-30

Fixes

• Start correcting arguement again

[1.16.8] - 2023-08-21

Fixes

• (action) With fetch-depth:0, don't ignore excludes and fail with spaces in file names

[1.16.7] - 2023-08-21

Fixes

• Provide more context for IO error messages

[1.16.6] - 2023-08-18

Fixes

• Provide more context for IO error messages

Commits

• 853cb28 chore: Release
• 75c2215 docs: Update changelog
• c4deebd Merge pull request #817 from epage/argue
• 8143c3b fix(dict): Treat arguement as a misspelling
• ca8ac80 chore: Update from '_rust/main' template
• a6ecf92 chore(renovate): Update config
• efe14d6 chore(renovate): Make style consistent
• e477391 chore: Release
• 7122823 docs: Update changelog
• 27fd226 Merge pull request #809 from epage/act
• 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 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)

[github-actions]

Review checklist

This checklist is meant to assist creators of PRs (to let them know what reviewers will typically look for) and reviewers (to guide them in a structured review process). Items do not need to be checked explicitly for a PR to be eligible for merging.

Purpose and scope

• The PR has a single goal that is clear from the PR title and/or description.
• All code changes represent a single set of modifications that logically belong together.
• No more than 500 lines of code are changed or there is no obvious way to split the PR into multiple PRs.

Code quality

• The code can be understood easily.
• Newly introduced names for variables etc. are self-descriptive and consistent with existing naming conventions.
• There are no redundancies that can be removed by simple modularization/refactoring.
• There are no leftover debug statements or commented code sections.
• The code adheres to our conventions and style guide, and to the Julia guidelines.

Documentation

• New functions and types are documented with a docstring or top-level comment.
• Relevant publications are referenced in docstrings (see example for formatting).
• Inline comments are used to document longer or unusual code sections.
• Comments describe intent ("why?") and not just functionality ("what?").
• If the PR introduces a significant change or new feature, it is documented in NEWS.md.

Testing

• The PR passes all tests.
• New or modified lines of code are covered by tests.
• New or modified tests run in less then 10 seconds.

Performance

• There are no type instabilities or memory allocations in performance-critical parts.
• If the PR intent is to improve performance, before/after time measurements are posted in the PR.

Verification

• The correctness of the code was verified using appropriate tests.
• If new equations/methods are added, a convergence test has been run and the results
  are posted in the PR.

Created with ❤️ by the Trixi.jl community.