Update @vardot/varbase-e2e to ^2.0.4

Problem/Motivation

Varbase AI asks for "@vardot/varbase-e2e": "^2", but the committed yarn.lock pins the harness at 2.0.3. CI installs from the lock, so the suite stays on the 2.0.3 steps whatever the constraint allows.

@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 2.0.x branch.
2. Run yarn install.
3. The installed harness is 2.0.3, not 2.0.4.

Proposed resolution

Set the constraint to ^2.0.4 and refresh yarn.lock, so the floor is stated and CI actually installs it. Bumping the constraint alone would change nothing, because the lock is what CI installs from.

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 9 scenarios and 30 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

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.