Update TracingResolver to accept Context parameter

[robertvansteen]

Summary

Updates the TracingResolver to accept a Context parameter in its resolve() and traced() methods, aligning with changes in the axiom library (v0.4.0). The resolver now manages inspector injection at the root level rather than during construction.

Key Changes

• Method signatures: Updated resolve(Source $source) to resolve(Source $source, Context $context) and traced(Source $source) to traced(Source $source, ?Context $context = null)
• Inspector management: Moved from constructor-time injection to root-level resolution, where the tree-aware inspector is swapped into the context only when needed
• Test updates: Refactored test helper createResolver() to remove symbol parameter and added new context() helper for creating contexts with definitions
• Symbol resolution: Changed from passing symbols to the resolver constructor to passing them via context definitions in individual test calls
• Documentation: Updated README with axiom v0.4.0 requirement and examples showing Context usage in resolve calls

Implementation Details

• The TracingResolver no longer registers itself as a ResolutionInspector in the container during construction
• Instead, at the root of each resolution, it creates a new Context with its tree-aware inspector if the provided context doesn't already have one
• This allows the inspector to be swapped in/out per resolution without affecting the resolver's configuration
• Recursive calls propagate the context unchanged, maintaining the tree structure throughout resolution
• All test cases updated to pass Context instances (with or without definitions) to resolve/traced calls

https://claude.ai/code/session_01YRTrWLWi2ethcHrQ4SraWZ