[SC-14192] Pin aiohttp[speedups] to avoid backports.zstd dependency

[juanmleng]

Pull Request Description

What and why?

What

Updated pyproject.toml to constrain aiohttp[speedups] to <3.13.1.

Why

aiohttp==3.13.1 starts pulling in backports.zstd (for Python < 3.14) via its packaging changes; keeping aiohttp below 3.13.1 avoids that new transitive dependency and helps prevent poetential downstream dependency conflicts.

How to test

Run poetry lock and confirm the resolved aiohttp version is <3.13.1 and that backports.zstd is not present in poetry.lock.

What needs special review?

Dependencies, breaking changes, and deployment notes

Release notes

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

[github-actions]

PR Summary

This PR introduces several functional enhancements and dependency updates along with minor code refactorings. The key changes include:

1. Dependency Upgrades:

   • Upgrades the version of aiohttp in the lockfile from 3.12.x to 3.13.0. The wheel files and associated hashes for aiohttp have been updated, ensuring compatibility with new releases.
   • Updates in the poetry lock file include several package updates (e.g. greenlet, Brotli, statsmodels) where new wheels and hashes are added. This helps ensure that binaries are built against newer versions and potentially gains performance and security enhancements.
   • Adjustments have been made to the zstandard package configuration in the lock file. The package is now marked as non-optional and its markers have been altered to include CPython (or when certain extras are used). This change ensures that zstandard is installed when required for high-performance scenarios.

2. Project Version Bump:

   • The version in pyproject.toml has been updated from 2.11.1 to 2.11.2, and the internal version file in validmind has been updated accordingly. This reflects the enhanced functionality and dependency updates that the project now includes.

3. Test Enhancements:

   • A list of additional scorer classes for classification and LLM deep evaluation has been added to the test types file. These include new scorers such as AbsoluteError, BrierScore, CalibrationError, and several deep evaluation metrics for LLMs. This expansion improves the coverage of scoring and evaluation of models within the project.

4. Code Refactoring:

   • In the tests load module, the function signature for retrieving test functions has been reformatted to improve readability. Additionally, the error message formatting in the same function has been streamlined.

Overall, the changes improve dependency management, expand test coverage by including more scoring strategies, and refine code readability.

Test Suggestions

• Run all unit and integration tests to verify that the dependency upgrades (especially aiohttp and zstandard) do not break existing functionality.
• Verify that the new test scorers are correctly registered and instantiated by the testing framework.
• Check the build process to ensure that new wheel artifacts are generated correctly with the updated hashes.
• Perform regression testing on functionality that relies on network operations using aiohttp.
• Ensure that the error handling in the tests load functions behaves as expected with missing test providers.