fix: #3616266 Show only the Feature / Scenario / Step output in the 9.2.x CI test logs

Problem/Motivation

The varbase-e2e suites print the Gherkin breakdown through @cucumber/pretty-formatter, but the JavaScript error reporter ran with an empty ignore, so every scenario appended a 10–20 line block of benign console noise:

[varbase-e2e] JavaScript errors during "Warm up the Home page across all breakpoints" (mode=warn):
  1. [console.error] Failed to load resource: the server responded with a status of 404 (Not Found)
  2. [console.error] Failed to load resource: net::ERR_CONTENT_LENGTH_MISMATCH
  … 23 more

That buries the Feature: text, the Scenario: lines and the steps, which is what a reader actually needs from a test job.

Proposed resolution

Adopt the same filter the 10.1.x suite already uses (which is why its logs read cleanly), env-overridable via VARBASE_E2E_JS_ERROR_IGNORE:

getComputedStyle|Failed to load resource|objectSizeSmall|plugincollection-plugin-not-found|CKEditorError|Maximum call stack size exceeded|ResizeObserver loop|importScripts|worker-html

JavaScript error reporting stays on (mode: 'warn', levels: ['error']) and genuine JavaScript errors are still reported — only the known-benign noise (missing optional assets, aborted preloads, editor plugin chatter) is filtered. A test job then reads as Feature / Scenario / Steps.

Part of issue #3616266.

AI-Generated: Yes

Checkpoints:

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