Re-assess E2E test

**Problem Description**
Around January 2026 when we updated Angular and tried to fix our other security issues, the E2E test kept failing and blocking our dependabot PRs. So we decided to take it out of the pipeline in the short term. We wanted to re-assess the usefulness of the E2E test but didn't have the opportunity at the time. This ticket returns to that question.

**Solution Needs**
- What is the value of the E2E test?
- What are the risks with keeping it alive?
- Should we continue to update it and have it as a check for PRs?
- What is required to fix it? Is that investment worth it?

**Timebox**
- How much effort are we committing to this research?

**Outcome**
Details describing the outcome of the research
- Was it successful? What direction should the work go?
- Was it unsuccessful? Discuss next steps with team

**Issues experienced**
- timing out
- failing to sync
- patch something to fix E2E, something else breaks, patch that, E2E breaks again , etc etc

Start by reviewing the E2E test and the pipeline configuration where it previously blocked Dependabot PRs. Examine the reported timeout, sync, and recurring-breakage problems, then document the test's value, risks, repair effort, and a recommendation for its future. Done means recording a clear outcome and next steps.

Written by the indexing model from the issue text.