Draft: Configure eslint job to output Code Quality report

What does this MR do?

Add Code Quality report output for the existing eslint job.

Note: This is truly a draft, and I can see that we might have to adapt it. For example, we might want to only output in this format in CI. But I'm pushing this MR to see what happens.

Related issues

Dogfood new direction for Code Quality in gitla... (#382153)

Checklist

Pre-merge

Consider the effect of the changes in this merge request on the following:

• Different pipeline types
• Non-canonical projects:
  • gitlab-foss
  • security
  • dev
  • personal forks
• Pipeline performance

If new jobs are added:

• Change-related rules (e.g. frontend/backend/database file changes): _____
• Frequency they are running (MRs, main branch, nightly, bi-hourly): _____
• Add a duration chart to https://app.periscopedata.com/app/gitlab/652085/Engineering-Productivity---Pipeline-Build-Durations if there are new jobs added to merge request pipelines

This will help keep track of expected cost increases to the GitLab project average pipeline cost per merge request RPI

Post-merge

• Consider communicating these changes to the broader team following the communication guideline for pipeline changes