fix: Fix issue with display of assertions when using custom messages

[tiago80673]

• Closes Custom assertion messages create confusing output in Cypress open #29167

Additional details

The display for assertion messages with a custom message was broken.
The regex pattern was made only for messages starting exactly with expected but they can start with a <custom message>:

Steps to test

Add to a test file:
expect(2).to.be.at.least(0, "Custom message")

How has the user experience changed?

Before:

After:

PR Tasks

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

[CLAassistant]

All committers have signed the CLA.

[cypress-app-bot]

• 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.

[jennifer-shehane]

This looks great. Tested locally on a failure also. Thanks for the contribution!

[AlexGuironnetRTE]

@tiago80673 Thanks a lot for fixing this!

[cypress-bot]

Released in 13.7.3.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v13.7.3, please open a new issue.