fix(opy): converge project preprocessing composition

[e54-bot]

Summary

• converge directory includes, nested include resolution, and stable cross-file source provenance
• resolve __script__ macro files relative to their definition file and honor open-document overlays
• preserve preprocessing state across include boundaries and report malformed macro declarations structurally
• add independent Issue Converge preprocessing and project-composition conformance exposed by #158 #161 project-composition coverage and keep the support matrix copies synchronized

Fixes #161

Validation

• cargo fmt --all -- --check
• cargo clippy --locked --workspace --all-targets --all-features -- -D warnings
• cargo test --locked --workspace --all-targets --all-features
• python3 -m unittest discover -s compatibility/tests
• offline conformance: 63 fixtures, compile-status 63/63 match, no new unowned preprocessing divergence

[Teakowa]

Major — crates/opy-rs/src/preprocess.rs:393

display_path canonicalizes/collapses .. components, so distinct overlay imports can be registered under the same HIR path. The existing alias_include_paths_are_distinct_imports case (shared.opy vs dir/../shared.opy) now produces two file IDs both named shared.opy, even though the overlays may contain different source. That breaks the cross-file provenance AC. Preserve a stable path identity that does not merge distinct imported sources.

Major — crates/opy-rs/src/preprocess.rs:761

resolve_script resolves the script against the definition file but stores the original declared path in ScriptMacro. Runtime errors therefore attribute a nested macro such as modules/nested/scripted.opy -> scripts/add.js only to scripts/add.js; two definition directories using the same relative script name become indistinguishable. The pinned OverPy reference stores the resolved getFilePaths(..., basePath)[0] path. Store/use the resolved project-relative path for runtime/diagnostic provenance.

[Teakowa]

LGTM