chore(deps-dev): bump cypress from 13.17.0 to 14.1.0 in the cypress group across 1 directory

[dependabot]

Bumps the cypress group with 1 update in the / directory: cypress.

Updates cypress from 13.17.0 to 14.1.0

Release notes

Sourced from cypress's releases.

v14.1.0

Changelog: https://docs.cypress.io/app/references/changelog#14-1-0

v14.0.3

Changelog: https://docs.cypress.io/app/references/changelog#14-0-3

v14.0.2

Changelog: https://docs.cypress.io/app/references/changelog#14-0-2

v14.0.1

Changelog: https://docs.cypress.io/app/references/changelog#14-0-1

v14.0.0

Changelog: https://docs.cypress.io/app/references/changelog#14-0-0

Commits

• 7ffd5a3 chore: release 14.1.0 (#31168)
• 2d80905 fix: corrects unit calculations in the slow network error message during Test...
• 63a9f88 chore: updating v8 snapshot cache (#31163)
• 3d9617c chore: updating v8 snapshot cache (#31162)
• 77e5219 chore: updating v8 snapshot cache (#31161)
• b4c7e40 dependency: update dependency compression to v1.8.0 (#31151)
• 1e7b596 misc: Add some missing types + Convert js driver/query tests to ts (#31154)
• 5da0995 feat: implement webdriver BiDi for Firefox versions 135 and greater (#30870)
• 0177508 chore: set up sharing of react via module federation in studio (#31129)
• a6e2efc chore: Update v8 snapshot cache - windows (#31157)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[netlify]

✅ Deploy Preview for eoxelements ready!

Name	Link
🔨 Latest commit	875678c
🔍 Latest deploy log	https://app.netlify.com/sites/eoxelements/deploys/67d948a1f96cb1000816c41b
😎 Deploy Preview	https://deploy-preview-1577--eoxelements.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[RobertOrthofer]

@silvester-pari I think that the cy.wrap is the correct way to test things asynchronously and avoid race conditions, so I am using this to rewrite all async tests, which are mainly tests that check for fired events after user interaction (e.g. via simulateEvent), or via programmatic actions.

There are some things that need additional clarification, because they could be broken already for some time:

• there is a flag named isDrawingEnabled, directly on the ol-layer that is drawn onto. This flag is checked in the drawend-hook and blocks the new feature to be added. Is there a benefit from using this instead of the active flag of the draw-Interaction?
• There is one thing we missed in this PR: we keep the active-state of the interaction when the layer is (re-)created, but we explicitly set the active-state to false when the layer is removed. I'd say we always keep the active-state, as an active select-Interaction without a visible layer will behave pretty much the same as an inactive one.
• I have removed an old test that's testing the behaviour of layers without ID, as Layer-IDs are not optional anymore. I hope that's ok for you.
• the general-test of the chart-Element is still failing for me in headless-mode, it seems like it's also an async-issue. If it's ok I can try to fix this here, but if it's only my machine then I wouldn't go too deep there, as it could also be a very hidden headless-canvas-rendering issue