[Feature]: Expose xcresult bundle path for further analysis

[NikitaKurpas]

Feature Description

Follow up to #284 (comment)

I would like the test/cov tools to expose the xcresult bundle path so that my agent can further extract additional data from it.

Use Cases

• When a UI test fails, Xcode captures a UI hierarchy tree and saves it to the bundle; my agent can then extract that tree and see what elements were present on the screen when the test failed
• Same applies for screenshots - the agent can just extract the screenshots from the failing test instead of rerunning the sim, trying the workflow itself, and then capturing screenshots

Example Interactions

(after the test failed)
[Me]: use the xcresulttool to extract the UI hierarchy tree from the xcresult bundle and inspect what was missing

(or better yet, create a skill to instruct the agent how to get the tree + provide a simple binary to extract screenshots from the xcresult bundle)

[cameroncooke]

Hi @NikitaKurpas great idea thanks for the suggestion!