Update @vardot/varbase-e2e to ^2.0.4

Problem/Motivation

The automated functional testing suite of this project pins its harness in package.json:

"@vardot/varbase-e2e": "~2.0.1"

@vardot/varbase-e2e 2.0.4 was published on 7 September 2026. It adds 17 built-in steps and fixes the existing HTTP status step.

This is a stale pin rather than breakage, and the issue should not be read as one. ~2.0.1 resolves to at least 2.0.1 and below 2.1.0, so a fresh install of this project today would in fact fetch 2.0.4. What the pin does not do is express the floor the suite now needs, and the committed yarn.lock resolves the harness at 2.0.3, so an existing checkout stays on the older steps.

Steps to reproduce

1. Check out the 1.0.x branch of this project.
2. Read the constraint: grep varbase-e2e package.json shows ~2.0.1.
3. Read the lock file: grep -A2 varbase-e2e yarn.lock shows the harness resolved at 2.0.3.

Proposed resolution

• Set the @vardot/varbase-e2e constraint in package.json to ^2.0.4.
• Refresh the committed yarn.lock with yarn install, which moves the resolved harness from 2.0.3 to 2.0.4.

What the project gains, per the 2.0.4 release notes:

• Access assertions, so a scenario can state what a role may and may not reach. This is directly useful here, where the module's own permissions decide who may reset a Canvas layout.
• Page title assertions.
• An added HTTP status code phrasing.
• A fix to the existing HTTP status step. It used to re-request the URL outside the browser, which lost the session cookies and followed redirects, so it asserted the status of a different request than the one under test. It is now session aware, which matters for this project's redirect and reset routes.
• A Drimage Improved step pack, which this project does not use today.

Verified locally on the change: node -e "console.log(require('@vardot/varbase-e2e/package.json').version)" prints 2.0.4, and npx cucumber-js --dry-run is clean over all 44 scenarios and 161 steps, with no ambiguous and no undefined steps. That is the evidence that the new library steps do not collide with anything this project defines locally.

AI-Generated: Yes

Remaining tasks

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

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• The automated functional testing suite now requires @vardot/varbase-e2e 2.0.4 or newer.