Fix Temporal resolver never reaching the concrete implementation

[thejesh23]

Linked issue

Closes #685

What & why

resolve_temporal_calls() builds implementors keyed by the bare interface name (Java INHERITS.target_qualified is bare) but looked it up with interface_qual, the fully-qualified name. Because interface_qual is always the qualified form, implementors.get(interface_qual, []) always returned [], the len(impls) == 1 branch was dead, and every Temporal stub call resolved to the interface method instead of the unique concrete implementation. callers_of() and impact analysis through the real implementation returned nothing.

This looks up implementors with the bare interface name — matching how it is keyed, and how the sibling Spring resolver already works.

How it was tested

uv run pytest tests/test_multilang.py -q -k Temporal   # 14 passed
uv run pytest tests/ --tb=short -q   # 1961 passed (1 pre-existing Windows/py3.14 failure, unrelated)
uv run ruff check code_review_graph/
uv run mypy code_review_graph/temporal_resolver.py --ignore-missing-imports --no-strict-optional   # Success

New test (fails on main, passes here):

• test_multilang.py::TestTemporalResolver::test_resolved_target_is_concrete_impl_not_interface — asserts a single-implementor stub call resolves to PaymentActivityImpl.charge, not the interface PaymentActivity.charge.

Checklist

• Tests added for new functionality
• All tests pass: uv run pytest tests/ --tb=short -q (one pre-existing, unrelated Windows/py3.14 failure)
• Linting passes: uv run ruff check code_review_graph/
• Type checking passes: uv run mypy code_review_graph/temporal_resolver.py --ignore-missing-imports --no-strict-optional
• Lines are at most 100 characters
• Docs updated where behavior changed (explanatory comment at the fix site)