Fix xcresult snapshot test file attribution

[dfrankland]

Summary

• Prefer structured failure summary file paths before falling back to call-stack inspection.
• Preserve the existing legacy documentLocationInCreatingWorkspace fallback path.
• Add a Swift SnapshotTesting xcresult fixture plus parameterized unit and integration coverage.

Rationale

Swift SnapshotTesting trait failures can include framework files later in the call stack, such as SnapshotsTestTrait.swift. The previous experimental failure-summary path selected the last Swift or Obj-C call-stack frame, so the reported JUnit file could point at SnapshotTesting internals instead of the test source that asserted the snapshot.

The xcresult failure summary already contains better structured attribution fields. Although the legacy schema calls the preferred field fileName, the inspected xcresult objects store a full absolute source path there, not just a basename. In the SnapshotTesting fixture, fileName and sourceCodeContext.location.filePath both point to /tmp/xcresult-snapshot-repro.sPh62f/Tests/SnapshotReproTests/SnapshotReproTests.swift; the call stack also includes full paths, but later frames point at SnapshotTesting internals.

This change therefore prefers fileName, then sourceCodeContext.location.filePath, and only falls back to the old call-stack heuristic when those structured fields are absent. The non-experimental legacy path remains available and unchanged in behavior.

Testing

• cargo test -p xcresult
• Temporarily reverted the source change and confirmed test_swift_snapshot_testing_trait_failure_uses_assertion_file::case_1_experimental_failure_summary fails by pointing at SnapshotsTestTrait.swift; restored the fix and confirmed it passes.

[trunk-io]

😎 Merged directly without going through the merge queue, as the queue was empty and the PR was up to date with the target branch - details.

[trunk-staging-io]

     

View Full Report ↗︎ ⋅ Docs

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.10%. Comparing base (5571a7c) to head (762b693).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1094      +/-   ##
==========================================
+ Coverage   81.77%   82.10%   +0.32%     
==========================================
  Files          69       69              
  Lines       14939    14986      +47     
==========================================
+ Hits        12217    12304      +87     
+ Misses       2722     2682      -40     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[TylerJang27]

Is this necessary?

[dfrankland]

Unfortunately, yes. We didn't correct for this before when parsing XCResult file:// URLS, so for test identity backwards compat, we need to continue percent encoding spaces to ensure we don't create new test cases.