feat: add resourceType support to cy.intercept() on req/routeMatcher

[flotwig]

• Closes cy.intercept by request cause #14525

User facing changelog

• Added the ability to match on resourceType with cy.intercept(), and to see the resource type of an intercepted request as req.resourceType.

Additional details

• All browsers report this in pre-request information to enable proxy logging, so we can now safely add it in the public intercept API too.
• In combination with cy.intercept(..., { log: false }, these two changes will unblock users on disabling/enabling logs by resource type: Is there an equivalent of cy.server({ignore: (xhr) => bool}) to disable logging, after moving to cy.intercept? #9358 (no PR yet for 9358)
• Also renamed "resourceType" to "requestedWith" everywhere it's used in multi-domain. Multi-domain was previously using the term "resource type" to refer to "xhr" or "fetch" for the runner patches, but this usage of the term clobbers the meaning given by CDP and makes it confusing. Since it's referred to as "requestedWith" in some places in MD already, I went ahead and renamed MD's usage to "requestedWith" for the entirety of MD.

Steps to test

Use the new resourceType property on RouteMatcher and req to match only certain requests:

cy.intercept({ resourceType: 'stylesheet' }) // only CSS

cy.intercept('/my-api', (req) => {
  expect(req.resourceType).to.eq('xhr') // only XHRs should hit the API
})

Possible values:

type ResourceType = 'document' | 'fetch' | 'xhr' | 'websocket' | 'stylesheet' | 'script' | 'image' | 'font' | 'cspviolationreport' | 'ping' | 'manifest' | 'other'

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• Has a PR for user-facing changes been opened in cypress-documentation? docs(api): add new resourceType properties to intercept.md cypress-documentation#4921
• Have API changes been updated in the type definitions?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[flotwig]

unrelated change, just noticed this while wrestling with debug

[cypress]

---

Test summary

4985 • 0 • 116 • 0 • 5

---

Run details

Project	cypress
Status	Passed
Commit	e46688a
Started	Dec 14, 2022 5:27 PM
Ended	Dec 14, 2022 5:40 PM
Duration	12:39 💡
OS	Linux Debian -
Browser	Chrome Beta 106

View run in Cypress Dashboard ➡️

---

Flakiness

	cookie_behavior.cy.ts		4
1	... > same site / cross origin > XMLHttpRequest > sets cookie on same-site request if withCredentials is true, and attaches to same-site request if withCredentials is true
2	... > same site / cross origin > fetch > sets same-site cookies if "include" credentials option is specified from request, but does not attach same-site cookies to request by default (same-origin)
3	... > same site / cross origin > XMLHttpRequest > sets cookie on same-site request if withCredentials is true, and attaches to same-site request if withCredentials is true
4	... > same site / cross origin > fetch > sets same-site cookies if "include" credentials option is specified from request, but does not attach same-site cookies to request by default (same-origin)
	commands/waiting.cy.ts		1
1	cy.origin waiting > alias > waits for the route alias to have a response

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[AtofStryker]

Looks good on my end! Thank you for renaming resourceType to requestedWith. I gave this a run against some of the tests in cypress-origin-providers and all checks out