Update @vardot/varbase-e2e to ^2.0.4

Problem/Motivation

Varbase Starter asks for "@vardot/varbase-e2e": "^2". That does not state the floor the suite now needs, and this project commits no lock file, so nothing records which harness version a checkout actually installed.

@vardot/varbase-e2e 2.0.4 was released on 7 September 2026 with 17 new built-in steps and one fix.

Steps to reproduce

1. Check out the 1.0.x branch.
2. Read the constraint: grep varbase-e2e package.json shows ^2.
3. Nothing states that the suite now expects the 2.0.4 steps.

Proposed resolution

Set the constraint to ^2.0.4. This project commits no lock file, so that one line is the whole change.

What this project gains:

• Access assertions, so a scenario can state what a role may and may not reach.
• 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, losing the session cookies and following redirects, so it asserted a different request than the one under test. It is now session aware.

Verified on the change: the harness installs at 2.0.4 and the dry run is clean across all 281 scenarios and 1921 steps, with nothing ambiguous and nothing undefined. Nothing in 2.0.4 collides with this project's own steps.

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 varbase_starter-1.0.1

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.