Bump restrictedpython from 6.2 to 7.3

[dependabot]

Bumps restrictedpython from 6.2 to 7.3.

Changelog

Sourced from restrictedpython's changelog.

7.3 (2024-09-30)

• Increase the safety level of safer_getattr allowing applications to use it as getattr implementation. Such use should now follow the same policy and give the same level of protection as direct attribute access in an environment based on RestrictedPython's safe_builtints.
• Prevent information leakage via AttributeError.obj and the string module.

7.2 (2024-08-02)

• Remove unneeded setuptools fossils that may cause installation problems with recent setuptools versions.
• Add support for single mode statements / execution.
• Fix a potential breakout capability in the provided safer_getattr method that is part of the safer_builtins.

7.1 (2024-03-14)

• Add support for the matmul (@) operator.

7.0 (2023-11-17)

Backwards incompatible changes ++++++++++++++++++++++++++++++

• Drop support for Python 3.6.

Features ++++++++

• Officially support Python 3.12.

Fixes +++++

• Prevent DeprecationWarnings from ast.Str and ast.Num on Python 3.12

• Forbid using some attributes providing access to restricted Python internals. (CVE-2023-37271)

• Fix information disclosure problems through Python's "format" functionality (format and format_map methods on str and its instances,

... (truncated)

Commits

• dc6c38f Preparing release 7.3
• 1087c68 Prepare release.
• d701cc3 Merge commit from fork
• 57a2acb additional check for safer_getattr (#285)
• d0e97cd Allow to use the package with Python 3.13.
• c5d5b74 Back to development: 7.3
• a5ab235 Preparing release 7.2
• b1ef5ba Prepare a release which does not yet support Python 3.13.
• 4eaa5fa safer_getattr (#282)
• d191a99 Remove setuptools fossils. (#281)
• 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[justinclift]

This is a major version jump (6.x to 7.x), but the RestrictedPython docs specifically say the only backwards incompatible change is the dropping of Python 3.6 support:

https://restrictedpython.readthedocs.io/en/latest/changes.html#backwards-incompatible-changes

So, in theory this PR looks like it shouldn't cause us any issues.