Bump codeanalyzer-python pin to 1.0.2 (Neo4j code property fix)

[rahlk]

codeanalyzer-python 1.0.2 is released with the fix for codellm-devkit/codeanalyzer-python#104: the Neo4j projection was writing every :PyClass/:PyCallable node without the code property (schema v2 moved source to per-module spans but the projector still read the removed field), which deadened py_code_fts and made PyNeo4jBackend.get_method_bodies (RETURN c.code) return nulls — breaking local ↔ Neo4j backend parity.

Action:

• Bump codeanalyzer-python==1.0.1 → ==1.0.2 in pyproject.toml dependencies and [tool.backend-versions] (version lockstep).
• Re-run the Python Neo4j backend parity tests (tests/analysis/python/test_python_neo4j_backend.py) against 1.0.2 — get_method_bodies should return real source again.

Filed from the propagation sweep of codellm-devkit/codeanalyzer-python#105.

[rahlk]

codeanalyzer-python 1.0.3 is being released with an additional fix on top of 1.0.2 — #107 (analysis-env provisioning now picks a parso-supported interpreter; on Python-3.14-default hosts the analysis no longer comes back silently empty). Bump the pin straight to codeanalyzer-python==1.0.3 and re-run both the Neo4j parity tests and the 3.14-host verification from codellm-devkit/codeanalyzer-python#107.