chore: bump minimum supported Python version to 3.11

[bowenliang123]

Checklist:

Important

Please review the checklist below before submitting your pull request.

• Please open an issue before creating a PR or link to an existing issue Upgrade Python version to 3.12, remove support for 3.10, and maintain compatibility with 3.11 and 3.12 #10399
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

Description

• drop the support for Python 3.10, support and tested with Python 3.11 and 3.12
• rerunning dev/reformat
  • to fix UP042 linter rule violations, auto fixed by with --unsafe-fixes
  • other linter auto fixes
• updated poetry lockfile, stripping dependency details for Python 3.10

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update, included: Dify Document
• Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement
• Dependency upgrade

Testing Instructions

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

[laipz8200]

Thank you for doing this great work.

IMO, the updates for GitHub Actions, documentation, and code should be separated into three PRs. Would you mind making this change?

There’s no need to rush, as we still need to test the new Python version.

[bowenliang123]

Thanks for the review. Python 3.11 brings performance improvements and many helpful features and typings.

As for your suggestion of separated PR, it seems that we still have to put them in one.
Once we raise the required minimum version in pyproject.toml project specification, it will immediately fail on Python 3.10 including:

• failed to install Python dependency via Poetry with Python version checks
• failed to pass Poetry's lockfile checks
• failed to pass Ruff linter checks, as Ruff runs the checking on different baseline on based minimum Python versions, especially for the UP pyupgrade rules

[cuckootan]

I think it's better to keep support python3.10, due to the great cost of upgrading docker image(and other parts).

[laipz8200]

@cuckootan We have to do this upgrade cause many new libraries require the new Python version. You can start preparing to do this upgrade from now on.