feat: Implemented eslint problem matcher

[work933k]

I propose to have NX-console-extension to support the VSCode problemmatcher functionality for eslint-tasks.

[MaxKless]

Thanks so much for submitting this PR! I'll look into it and give it a try :)

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit b66c7ea. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 4 targets

• nx affected --t=test,build,e2e --configuration=ci
• nx affected --t=lint,test,build,e2e --configuration=ci
• nx-cloud record -- ./gradlew ktfmtCheck
• nx-cloud record -- npx nx format:check

---

Sent with 💌 from NxCloud.

[MaxKless]

Thanks for the PR! It works great when running tasks from the project view.
However, there's additional places we should consider:

• using the Nx: run and Nx: run target commands should also populate the problems pane
• running the target from the tooltip in the integrated graph & project details view should also populate the problems pane
• running the target from the Generate & Run Target view should also populate the problems pane

I think the easiest solution here is to check for the problemMatchers right inside CliTaskProvider.executeTask. You can use the positional argument when command === run, split it by : and check if it's a lint target. In that case, pass the problem matchers to the task.

Thanks a lot for this contribution it rocks!

P.S. also make sure to format your code with npx nx format --fix to make sure it passes CI :)