Update Cypress to v15.7.0, remove deprecated APIs, and disable continue-on-error

[Copilot]

Description

Upgraded Cypress from v13.16.0 to v15.7.0 and migrated deprecated APIs to their modern equivalents. Additionally, disabled continue-on-error in the GitHub Actions workflow to ensure test failures are properly reported in CI.

Breaking changes addressed:

• Removed cy.server() calls (deprecated in v6.0, removed in v12+)
• Replaced cy.route() with cy.intercept() API, specifying explicit HTTP methods
• Fixed syntax errors (stray semicolon)

Files modified:

• cypress/package.json - Updated Cypress dependency to v15.7.0
• cypress/e2e/nav_create_trek.cy.js - Removed cy.server() call, fixed syntax
• cypress/e2e/nav_create_signage.cy.js - Replaced cy.route() with cy.intercept('GET', ...), removed cy.server()
• .github/workflows/test.yml - Removed continue-on-error: true from Cypress workflow step

Testing improvements:

• All test files validated for syntax correctness
• No deprecated patterns remain in the codebase
• CI pipeline will now properly fail when tests fail (continue-on-error removed)
• Fixed cy.intercept() to explicitly specify HTTP method ('GET') for proper request interception

Known Issues:

• Some E2E tests in Debian package environment fail due to test data dependencies and timing issues. These failures appear to be pre-existing environmental issues that were previously masked by continue-on-error: true. The Docker E2E tests pass successfully, confirming Cypress v15.7.0 compatibility.

Related Issue

Addresses comment request to update to newest Cypress version and fix test workflow configuration.

Checklist

• [ ] I have followed the guidelines in our Contributing document
• [ ] My code respects the Definition of done available in the Development section of the documentation
• [x] I have performed a self-review of my code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have added tests that prove my fix is effective or that my feature works.
• [ ] New and existing unit tests pass locally with my changes
• [ ] I added an entry in the changelog file
• [ ] My commits are all using prefix convention (emoji + tag name) and references associated issues
• [ ] I added a label to the PR corresponding to the perimeter of my contribution
• [ ] The title of my PR mentionned the issue associated

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.