Add Python 3.14 support

[teta2k]

Summary

• extend the supported Python range through Python 3.14 in package metadata, documentation, and the runtime version gate
• update locked native dependencies to versions that install on Python 3.14 while preserving compatible versions for older Python releases
• add Python 3.14 to unit, end-to-end, benchmark, lint, smoke, and QA coverage
• add focused coverage for the supported/unsupported version boundary

Root cause

Python 3.14 was explicitly rejected by the runtime version guard, causing protect() to return without enabling the agent. The existing lock also selected native dependency versions that do not build on Python 3.14, notably older pydantic-core/jiter and psycopg2-binary releases.

Impact

The agent can now install and run on Python 3.14, while Python 3.15 and later remain explicitly unsupported until validated.

Validation

• Python 3.14.6: poetry check
• Python 3.14.6 full unit suite: 1565 passed, 17 skipped
• focused version-gate tests: 3 passed
• Black and Pylint: passed
• Compose-native QA suite: 24/34 passed
  • two additional full-load failures passed when rerun in isolation
  • the remaining test-bypassed-ip failure reproduced identically with Python 3.13, so it is not Python-3.14-specific
  • seven failures match the existing shared Compose harness baseline

Summary by Aikido

Security Issues: 0	Quality Issues: 0	Resolved Issues: 0

⚡ Enhancements

• Enabled Python 3.14 across CI workflows, Dockerfile, and templates
• Expanded runtime version check to permit Python 3.14
• Added GIL-disabled detection and prevented running without GIL enabled

🐛 Bugfixes

• Avoided forkserver-induced re-imports when starting background process on Python 3.14

^{More info}