Build and publish Cypress suite

[torchiaf]

Summary

Fixes #16057

Occurred changes and/or fixed issues

This pull request introduces the new @rancher/cypress package, which modularizes and standardizes Cypress E2E test utilities, configuration, and page objects for Rancher Dashboard.
The changes include extracting a reusable Cypress base configuration, updating import paths for better compatibility, and adding documentation and packaging infrastructure for the new package. Additionally, several minor improvements and bug fixes are applied to the E2E test suite.

It also adds a GitHub Actions workflow (.github/workflows/release-cypress-pkg.yaml) for automated building and publishing of the Cypress package to npm on new release tags.

Please, take a look to the README.md file for a better insight.

Technical notes summary

• The release workflow successfully published new @ rancher/cypress packages on NPM: https://github.com/rancher/dashboard/actions/runs/20265134941

Areas or cases that should be tested

Areas which could experience regressions

@yonasberhe23 @izaac not sure how to verify regressions in the Jenkins environment. Could you take a look ?

Tests

• Build the new package locally

cd cypress
yarn install
yarn build-pkg
cd dist && yarn install && yarn link

• Link the pkg in a consuming project (e.g. a new extension)

yarn link @rancher/cypress

# These commands are only for yarn linked packages - npx rancher-cypress cli is available when installing from npm.
./node_modules/@rancher/cypress/bin/cli.js init
./node_modules/@rancher/cypress/bin/cli.js open

• Use the NPM version

yarn add @rancher/cypress --dev

npx rancher-cypress init
npx rancher-cypress open

• Add some new tests, the POs and commands should be available in your project

Screenshot/Video

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

[torchiaf]

@cnotv I added some missing library and fixed minor issues in the template files, nothing impacting the building process though.

[torchiaf]

This will block the CI gates if there is a Typescript error in ./cypress dir.

[rak-phillip]

I'd recommend configuring trusted providers at this point, otherwise we will need to schedule token refreshes on a regular interval; tokens have a maximum lifespan of three months as of November/December.

In order to do this, we need to configure the package in npm:

https://docs.npmjs.com/trusted-publishers

And then ensure that we fetch tokens using oidc in our release workflow:

#16166

[torchiaf]

I pushed the changes, and @richard-cox assigned the trusted publisher to @rancher/cypress.
I tried to push a new version from a dev branch, but I got an authentication error, probably my workflow is not creating an OIDC token (which is required by npm publish now) as it's not running on master.

So, i would test again the release workflow after we merge the PR.

[rak-phillip]

If that doesn't work, we may need to include the line to update npm:

      # Ensure npm 11.5.1 or later is installed
      - name: Update npm
        run: npm install -g npm@latest

It appears to be missing from the workflow and will be required for the short-term.

[cnotv]

I think you miss --access public

Note that for legacy reasons scoped packages are by default published with an access set to restricted (aka "private packages"). This requires you to register for a paid npm plan. In case you simply wish to publish a public scoped package to the registry (for free), just add the --access public flag. This behavior can be enabled by default through the npmPublishAccess settings.

https://yarnpkg.com/cli/npm/publish#details

[torchiaf]

No, the flag is there:

PUBLISH_ARGS="--no-git-tag-version --access public --registry $NPM_REGISTRY"

https://github.com/torchiaf/dashboard/blob/9cb1ddb10e4ec608963de5524d589ce978b347df/cypress/scripts/publish.sh#L54

[aalves08]

LGTM

[yonasberhe23]

@torchiaf the Jenkins Cypress config file (cypress/jenkins/cypress.config.jenkins.ts) is independent and doesn't import the modified base-config.ts or cypress.config.ts, so these changes won't affect our CI/CD pipeline.