fix: Explain error thrown when cypress commands in .should() callback

[BlueWinds]

Associated code: https://github.com/cypress-io/cypress/pull/23734

Beginning in Cypress 11, invoking Cypress commands inside .should() will throw an error. Doing this currently (Cy 10 and earlier) results in undefined behavior - a term which should scare anyone familiar with it from other programming languages.

We're resolving this by throwing an error, disallowing the situation entirely. This is a breaking change, which is why it's going out in 11.0.0.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
cypress-documentation	✅ Ready (Inspect)	Visit Preview	Oct 11, 2022 at 9:47PM (UTC)

[flotwig]

@lmiller1990 @BlueWinds I'd just go ahead and get an 11.0.0 branch/PR up, so we don't have to keep track of this until then. It might be a while til it's ready since I believe we're waiting on multidomain GA to drop 11.0.0.