[Aikido] Fix critical issue in anyio via minor version upgrade from 4.13.0 to 4.14.2

[aikido-autofix]

Upgrade anyio to fix critical TLS hostname validation vulnerability where IDNA 2003 encoding could allow certificate validation bypass or rejection.

✅ 1 CVE resolved by this upgrade, including 1 critical 🚨 CVE

This PR will resolve the following CVEs:

Issue	Severity	Description
AIKIDO-2026-889297	🚨 CRITICAL	[anyio] TLSStream.wrap() uses outdated IDNA 2003 instead of IDNA 2008 for hostname resolution, causing mismatches between intended and validated hostnames. This enables certificate validation bypass or rejection, potentially allowing man-in-the-middle attacks or legitimate connection failures.

🔗 Related Tasks

• https://corvaqa.atlassian.net/browse/FORTI-156

🤖 Remediation details

Fix critical security vulnerability in anyio transitive dependency

Short summary

This PR remediates a critical vulnerability in anyio (AIKIDO-2026-889297), a transitive dependency resolved in uv.lock. No changes were required to pyproject.toml; the fix was applied entirely through a lockfile-only upgrade via uv lock --upgrade-package anyio.

anyio

anyio is pulled in transitively by httpx, which is a direct dependency of corva-api-client. Versions of anyio from 0.0.1 through 4.14.1 are affected by a critical vulnerability; the patched version is 4.14.2. Because httpx's existing dependency specification already permitted the newer anyio release, no manifest edits were necessary — running uv lock --upgrade-package anyio was sufficient to resolve the lockfile to the patched version 4.14.2.

Version changes

Package	From	To	Why updated
anyio	4.13.0	4.14.2	Transitive CVE fix (via httpx); lockfile-only upgrade