build(deps): update sqlparse requirement from ~=0.5.1 to ~=0.5.3

[dependabot]

Updates the requirements on sqlparse to permit the latest version.

Changelog

Sourced from sqlparse's changelog.

Release 0.5.3 (Dez 10, 2024)

Bug Fixes

• This version introduces a more generalized handling of potential denial of service attack (DOS) due to recursion errors for deeply nested statements. Brought up and fixed by @​living180. Thanks a lot!

Release 0.5.2 (Nov 14, 2024)

Bug Fixes

• EXTENSION is now recognized as a keyword (issue785).
• SQL hints are not removed when removing comments (issue262, by skryzh).

Release 0.5.1 (Jul 15, 2024)

Enhancements

• New "compact" option for formatter. If set, the formatter tries to produce a more compact output by avoiding some line breaks (issue783).

Bug Fixes

• The strip comments filter was a bit greedy and removed too much whitespace (issue772). Note: In some cases you might want to add strip_whitespace=True where you previously used just strip_comments=True. strip_comments did some of the work that strip_whitespace should do.
• Fix error when splitting statements that contain multiple CASE clauses within a BEGIN block (issue784).
• Fix whitespace removal with nested expressions (issue782).
• Fix parsing and formatting of ORDER clauses containing NULLS FIRST or NULLS LAST (issue532).

Release 0.5.0 (Apr 13, 2024)

Notable Changes

• Drop support for Python 3.5, 3.6, and 3.7.
• Python 3.12 is now supported (pr725, by hugovk).
• IMPORTANT: Fixes a potential denial of service attack (DOS) due to recursion error for deeply nested statements. Instead of recursion error a generic

... (truncated)

Commits

• ec0af5b Update version number.
• c81cdf9 Disable checks for pypy-3.8.
• a31245e Update changelog.
• bbd8f51 Generalize RecursionError handling.
• e57923b Switch back to development.
• 7084df8 Add support for Python 3.13.
• 5f37dd6 Bump version to 0.5.2.
• 7c70674 Update authors and changelog.
• 48bd14e [feature] returning .gitignore to previous version
• 2f9c7ec [feature] deleting envs from .gitignore, creating test for SQL-Hints
• 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.