Update @vardot/varbase-e2e to ^2.0.4

Problem/Motivation

Varbase Project Template 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 no matter what the constraint allows.

On this project the lock is in worse shape than that. yarn install --immutable already fails on it today, before any change, with "The lockfile would have been modified by this install, which is explicitly forbidden", because the lock still carries 181 CKEditor 5 entries that package.json no longer requires. That drift is pre-existing.

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

Steps to reproduce

1. Check out the 11.0.x branch.
2. Run yarn install. The installed harness is 2.0.3.
3. Run yarn install --immutable. It fails on the stale lock.

Proposed resolution

Set the constraint to ^2.0.4 and refresh yarn.lock, so the floor the suite needs is stated and CI actually installs it. Refreshing the lock also prunes those 181 stale CKEditor 5 entries, which is what makes --immutable pass again. That pruning is a correction of pre-existing drift, not new scope.

What the 291 scenarios in this project gain:

• 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 291 scenarios and 1963 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_project-11.0.7

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, and the lock file is valid for an immutable install again.