[Automation] - Declare the Cypress reporting and tag filtering packages

[izaac]

Summary

CI only change, no product code affected.

Occurred changes and/or fixed issues

The Jenkins E2E job needs five packages this branch does not declare: cypress-multi-reporters and mocha-junit-reporter write the JUnit XML, junit-report-merger merges it into results.xml, and find-test-names and globby pre-select specs by tag. release-2.15 and master declare all five, so this is the only branch that needs anything added at run time.

Declaring them here makes a run install exactly what --frozen-lockfile pins, and nothing else, the same way release-2.15 already does.

Technical notes summary

• Five entries in cypress/package.json, at the versions release-2.15 and master already use, plus the regenerated lockfile.
• The lockfile change is additive. No existing pin moves and nothing is dropped, so Cypress stays at 11.1.0 and @cypress/grep at 3.1.5.
• Nothing in cypress/jenkins/ changes. The job keeps working either way; this only moves where the packages come from.

Testing done

yarn install --frozen-lockfile in the container the E2E job uses, node 24.14.0 and yarn 1.22.22:

frozen install PASSES
  cypress                        11.1.0
  @cypress/grep                  3.1.5
  cypress-mochawesome-reporter   3.8.2
  cypress-multi-reporters        1.6.4
  mocha-junit-reporter           2.2.1
  junit-report-merger            9.0.3
  find-test-names                1.29.19
  globby                         11.1.0
  jrm 9.0.3

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility
• The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base