chore: upgrade dependency lockfiles to resolve dependabot alerts

[Flix6x]

Resolves all 46 open dependabot alerts (https://github.com/FlexMeasures/flexmeasures-s2/security/dependabot), which all live in the pip-compile lockfiles rather than in real dependency declarations.

Changes:

• Recompiled requirements/{app,test,dev}.txt with pip-compile --upgrade, using Python 3.11 to match CI (the previous lock was compiled with 3.12). Notable bumps: Pillow 11.1.0 → 12.3.0 (it's transitive via flexmeasures → darts → matplotlib, so it can't simply be removed), werkzeug 3.1.8, flask 3.1.3, flask-cors 6.0.5, jinja2 3.1.6.
• Dropped the obsolete pre-commit/virtualenv pins in dev.in — they existed only because FlexMeasures used to hard-pin its dependencies (FlexMeasures should not pin its dependencies in the Pypi distribution flexmeasures#648), which it no longer does. This lets virtualenv resolve past its alert threshold.
• Bumped black 22.10.0 → 25.1.0 (alert wants ≥24.3.0) in both dev.in and .pre-commit-config.yaml; the only resulting reformat was an ellipsis-class stub in scheduler/schemas.py, rewritten as pass to keep flake8 happy.

Tests pass locally with the upgraded environment.

🤖 Generated with Claude Code

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	pypi/​tqdm@​4.69.0
	pypi/​certifi@​2024.12.14 ⏵ 2026.7.22	+1
	pypi/​lunardate@​0.2.2 ⏵ 0.3.0	+1
	pypi/​numpy@​1.26.4 ⏵ 2.4.6	+1
	pypi/​openturns@​1.24 ⏵ 1.27.post1	+1
	pypi/​pillow@​11.1.0 ⏵ 12.3.0		+75
	pypi/​psycopg2-binary@​2.9.10 ⏵ 2.9.12
	pypi/​scipy@​1.15.1 ⏵ 1.17.1	+1
	pypi/​tldextract@​5.1.3 ⏵ 5.3.1	+1
	pypi/​pathspec@​0.12.1 ⏵ 1.1.1	+1
	pypi/​matplotlib@​3.10.0 ⏵ 3.11.1	+1
	pypi/​mypy@​1.14.1 ⏵ 2.3.0	+1
	pypi/​numba@​0.66.0
	pypi/​scikit-learn@​1.5.2 ⏵ 1.7.2	+1
	pypi/​times@​0.7
	pypi/​pandas@​2.2.1 ⏵ 2.3.3	+1
	pypi/​dill@​0.3.9 ⏵ 0.4.1	+1
	pypi/​libpass@​1.9.3
	pypi/​dnspython@​2.7.0 ⏵ 2.8.0	+1
	pypi/​sktime@​0.35.0 ⏵ 1.0.1	-9
	pypi/​black@​22.10.0 ⏵ 25.1.0	-2	+2
	pypi/​fonttools@​4.55.3 ⏵ 4.63.0		+2			-9
	pypi/​pytest@​8.3.4 ⏵ 9.1.1	-3	+2
	pypi/​patsy@​1.0.1 ⏵ 1.0.2	+1
	pypi/​flask@​3.1.0 ⏵ 3.1.3		+2
	pypi/​pycparser@​2.22 ⏵ 3.0	-8
	pypi/​statsmodels@​0.14.4 ⏵ 0.14.6	+1
	pypi/​joblib@​1.4.2 ⏵ 1.5.3
	pypi/​xarray@​2026.7.0
	pypi/​sentry-sdk@​2.19.2 ⏵ 2.66.1	-5
	pypi/​distlib@​0.3.9 ⏵ 0.4.3	+1
	pypi/​tzdata@​2024.2 ⏵ 2026.3
See 115 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: pypi dill is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: requirements/app.txt → pypi/dill@0.4.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/dill@0.4.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: pypi pycparser is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: requirements/app.txt → pypi/pycparser@3.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pycparser@3.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: pypi pycparser is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: requirements/app.txt → pypi/pycparser@3.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/pycparser@3.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report