fix(deps): regenerate runtime lock

[tianrking]

Summary

• regenerate the Python 3.11 universal, hash-verified runtime lock
• resolve the incompatible caio, pydantic-core, and websockets pins reported in requirements-lock.txt has multiple broken pins causing --require-hashes to fail (caio, websockets, pydantic-core) #558

Root cause and impact

The previous lock selected versions outside the constraints required by aiofile, pydantic, and langgraph-sdk. That makes the Docker image's pip install --require-hashes step fail before the service starts.

Validation

• python -m uv pip compile agent/requirements.txt --generate-hashes --universal --python-version 3.11 -o requirements-lock.txt
• python -m uv pip install --dry-run --python-version 3.11 --python-platform linux --require-hashes -r requirements-lock.txt
• git diff --check

Scope and risk

This only refreshes dependency resolution; it does not change broker, credential, MCP, or trading code. Docker is unavailable on this host, so the image build was not run. Reverting this commit restores the previous lock.

Fixes #558

[warren618]

Merged — thanks for tracking down the exact pins. Verified independently: reproduced the original --require-hashes failure against main's lockfile, then confirmed this PR's regenerated lockfile resolves cleanly (caio 0.9.25, websockets 15.0.1, pydantic-core 2.46.4 — matching what issue #558 needed). Appreciate the fix.