build(deps): bundle all Python dependency updates

[pdettori]

Summary

Bundles 15 Dependabot PRs into a single update with regenerated uv.lock files. The individual Dependabot PRs all failed CI because uv.lock was stale (--locked flag rejects mismatched lockfiles).

file_organizer

• a2a-sdk >=0.2.16 → >=0.3.26
• langchain-core >=1.2.11 → >=1.2.31
• langchain-community >=0.3.27 → >=0.4.1
• openinference-instrumentation-langchain >=0.1.36 → >=0.1.62
• python-keycloak >=5.5.1 → >=7.1.1

weather_service

• a2a-sdk >=0.2.16 → >=0.3.26
• langchain-core >=1.2.11 → >=1.2.31
• langchain-community >=0.3.27 → >=0.4.1
• langchain-ollama >=0.2.1 → >=1.1.0
• python-keycloak >=5.5.1 → >=7.1.1

image_service

• langchain-community >=0.3.27 → >=0.4.1
• langchain-ollama >=0.2.1 → >=1.1.0
• langchain-mcp-adapters >=0.1.0 → >=0.2.2
• pydantic-settings >=2.8.1 → >=2.13.1
• python-multipart >=0.0.22 → >=0.0.26

Supersedes

#236, #237, #238, #239, #240, #241, #242, #243, #244, #245, #246, #247, #248, #249, #250

Test plan

• CI test-startup passes (lockfiles are now in sync)
• lint and test jobs pass
• Verify agents start correctly with updated dependencies

[pdettori]

Note on Trivy check failure: This is the GitHub Advanced Security / code scanning check (separate from our trivy-scan CI job which passed). It reports 87 alerts (3 critical, 19 high, 42 medium, 23 low) but these are not introduced by this PR — the check summary itself notes:

Alerts not introduced by this pull request might have been detected because the code changes were too large.

The large uv.lock diffs triggered a full Trivy rescan which surfaced pre-existing vulnerabilities in transitive dependencies. This is a known behavior when lockfile changes touch many packages.

Tracking separately in a dedicated issue.

[pdettori]

Tracking Trivy code scanning failures in #253.

[maia-iyer]

LGTM - the failing test is being tracked. We can merge and iterate