Switch the Varbase Core functional testing suite to Varbase E2E (10.1.x, 9.2.x)

Problem/Motivation

The Varbase Core functional testing suite still installs the browser testing package the suite was originally built on. That package is no longer the one Vardot maintains: the harness now ships as @vardot/varbase-e2e on npm, released from Vardot/varbase-e2e, and the Varbase projects and site templates have moved to it.

Steps to reproduce

Read the 10.1.x and 9.2.x branches: the testing dependency, the step-definition require paths and the CI configuration all name the old package.

Proposed resolution

• Depend on @vardot/varbase-e2e and load its step definitions in the cucumber configuration.
• Point the report generator at the new package path and rename the world parameter environment variables to the VARBASE_E2E_ prefix.
• Update the suite documentation, the spelling dictionary and the ignore rules to match.

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

• The functional testing suite now runs on @vardot/varbase-e2e.