Issue #3576093: Fix lint errors in GitLab UI even when pipeline is green.

Description

See Fix eslint errors in GitLab UI even when pipeli... (#3576093 - closed) • Unassigned • Infrastructure

Testing instructions

1. Check CI pipeline for any MR with all green pipeline
2. Look for errors/warnings shown even though the pipeline is green:

Test summary: 3 failed, 665 total testsphpcs: no changed test results, 116 total testsphpstan: no changed test results, 1 total testphpstan (max PHP version): no changed test results, 1 total testeslint: 3 failed, 27 total testsorg.eslint.max-lenorg.eslint.max-lenorg.eslint.max-lenphpunit: no changed test results, 260 total testsphpunit (max PHP version): no changed test results, 260 total tests

Checklist

• I have updated the MR title to use format: Issue #1234: My issue title.
• I have updated the MR description to include: Closes #1234
• I have performed a self-review of my own code
• I have updated documentation for any new or changed functionality
• I have written testing instructions and verified them locally

Not applicable:

• I have added or updated tests, or explained in the description why this change is not covered by tests
• I have noted any required post-merge steps (config imports, cache rebuilds, manual changes)
• This MR contains no breaking API or hook changes, or they are explicitly documented in the description

AI Compliance

Note

Check the one that best describes your usage, or leave all unchecked if AI was not significantly used.

• AI Assisted Code
  Mainly written by a human; AI used for autocomplete or partial generation under full human supervision.

• AI Generated Code
  Mainly generated by AI, reviewed and approved by a human before this MR was created.

• Vibe Coded
  Generated by AI and only functionally reviewed before this MR was created.

Closes #3576093 (closed)