task: Switch the Varbase functional testing suite to Varbase E2E

Problem/Motivation

The Varbase functional testing suite on this project still depends on the previous testing package. The harness now ships as Varbase E2E (@vardot/varbase-e2e 2.0.1 on npm, maintained by Vardot) and includes the Drupal and Varbase step packs as built-ins.

Steps to reproduce

grep -rn webship package.json cucumber.js .gitlab-ci.yml on the 4.0.x, 3.1.x and 3.0.x branches.

Proposed resolution

• Depend on @vardot/varbase-e2e.
• Update the require: globs in cucumber.js and the helper imports in the step definitions.
• Rename the CI test job to varbase-e2e-test and the environment variables to the VARBASE_E2E_* family.
• Produce the HTML + PDF report the same way the Varbase Project pipeline does.
• Remove any local copies of steps the package now ships as built-ins.
• Apply on: 4.0.x, 3.1.x, 3.0.x.

Remaining tasks

• ✅ File an issue
• ❌ Addition/Change/Update/Fix
• ❌ Testing to ensure no regression
• ➖ Automated unit testing coverage
• ❌ Automated functional testing coverage
• ➖ UX/UI designer responsibilities
• ❌ Readability
• ➖ Accessibility
• ➖ Performance
• ➖ Security
• ➖ Developer Documentation
• ➖ User Guide Documentation
• ➖ Reviewed by human
• ➖ Code review by maintainers
• ➖ Full testing and approval
• ➖ Credit contributors
• ➖ Review with the product owner
• ➖ Release notes snippet
• ✅ Release

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• Automated functional testing on this project now runs on Varbase E2E.

AI-Generated: Yes