fix: (studio) remove itGrep lines from stack trace when determining invocationDetails

[astone123]

Additional details

This PR fixes the invocation details when it has been re-written as itGrep which happens in the @cypress/grep and @bahmutov/cy-grep plugins. This allows us to determine the correct invocation details for the test.

Steps to test

I tested this with the @bahmutov/cy-grep package. Install the package and register it in your support file in accordance with the documentation. Open Cypress Studio by clicking the "edit in studio" button next to a test. Verify that the test content is loaded correctly and you can edit and save the test as expected.

How has the user experience changed?

Users of @bahmutov/cy-grep package can now use studio as intended

PR Tasks

• Have tests been added/updated?
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

---

Note

Removes itGrep frames from error stacks to correctly resolve invocation details, with a unit test covering grep-modified stacks.

• Driver:
  • Stack processing: Add stackWithGrepLinesRemoved to filter lines containing itGrep.
  • Invocation details: Update getInvocationDetails to drop itGrep frames after trimming to spec frames.
• Tests:
  • Add unit test ensuring grep-modified stack traces resolve to the correct spec file/line via getSourcePosition.

^{Written by Cursor Bugbot for commit b6bc0f5. This will update automatically on new commits. Configure here.}

[cypress]

cypress    Run #66904

Run Properties:   Passed #66904  •  b6bc0f5637: Merge branch 'develop' into astone123/fix-itgrep-trace

Project	cypress
Branch Review	astone123/fix-itgrep-trace
Run status	Passed #66904
Run duration	19m 56s
Commit	b6bc0f5637: Merge branch 'develop' into astone123/fix-itgrep-trace
Committer	Adam Stone-Lord
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	15
Pending	1102
Skipped	4
Passing	26755
View all changes introduced in this branch ↗︎

---

Warning

Partial Report: The results for the Application Quality reports may be incomplete.

UI Coverage  45.61%
Untested elements	187
Tested elements	161

Accessibility  97.98%
Failed rules	4 critical   8 serious   2 moderate   2 minor
Failed elements	101

[astone123]

@mschile @mabela416
After looking at fixing this on the cloud side for a bit, I think the best way to handle the grep stack issue is with a solution like this on the app side. We use the invocation details in various places across the app to decide which test to focus in studio mode and other things, so normalizing the stack on the cloud side doesn't fix the issue entirely. Let me know what you think

[mabela416]

I tested it locally and it works

[AtofStryker]

Likely good to reference what itGrep is and where it is coming from (same with above) https://github.com/cypress-io/cypress/blob/develop/npm/grep/src/register.ts#L77. people who aren't familiar with @cypress/grep will struggle to understand what this means.

The other concern I have is that there could be something legitimate in the stack that has itGrep in it that we want to capture but are omitting it here. Or is this only considered when trying to calculate the row/column in the spec file where the error occurred?