Bug: When executing cross-module dependencies like
"parent: submodule::recipe", the dependency recipe was executed with
the root module's ExecutionContext instead of the submodule's context.
This caused submodule recipes to run in the wrong working directory.

Root cause: The dependency execution logic in run_dependencies() used
the same ExecutionContext for all dependencies regardless of which
module they belonged to.

Solution: Added create_dependency_context() method that:
1. Analyzes recipe namepaths to detect cross-module dependencies
2. Navigates module hierarchy to find the correct submodule
3. Creates new ExecutionContext with proper submodule reference
4. Ensures dependencies execute in their correct module context

This fixes both normal module recipes (now run in submodule directory)
and [no-cd] module recipes (now run in invocation directory as intended)

Add comprehensive tests to verify the working directory fix for
cross-module dependencies:

- cross_module_dependency_runs_in_submodule_directory: Tests that normal
  cross-module dependencies execute in the correct submodule directory
- cross_module_dependency_with_no_cd_runs_in_invocation_directory: Tests
  that [no-cd] cross-module dependencies execute in the invocation
  directory
- nested_cross_module_dependency_runs_in_correct_directory: Tests that
  deeply nested module dependencies work correctly

These tests verify that the fix properly resolves the module working
directory bug where cross-module dependencies were executing with the
wrong ExecutionContext.