Rust: Account for disambiguation in path resolution tests

[hvitved]

No description provided.

[Copilot]

Pull request overview

This pull request updates the path resolution tests to properly account for disambiguation when resolving function call paths in Rust. The changes use CallExpr.getResolvedTarget() instead of resolvePath() for paths that are function expressions in call sites, which provides more accurate resolution when multiple implementations are available.

Changes:

• Modified the path resolution query and test utility to use getResolvedTarget() for call expression function paths
• Updated test expectations to reflect the new, more accurate path resolutions
• Updated test input comments to document expected vs. spurious resolutions

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
rust/ql/test/library-tests/path-resolution/path-resolution.ql	Added logic to distinguish call expression paths and use getResolvedTarget() for disambiguation
rust/ql/lib/utils/test/PathResolutionInlineExpectationsTest.qll	Applied the same disambiguation logic to the inline expectations test
rust/ql/test/library-tests/path-resolution/path-resolution.expected	Updated expected test results to reflect the new resolution behavior
rust/ql/test/library-tests/path-resolution/main.rs	Updated test comments to reflect which resolutions are now found vs. missing