tasks: Use valid column when creating range for problem matcher

[msujew]

What it does

When calling Range.create with a value larger than > 2^32-1, the function will throw an error. We do this when building ranges parsed from matched problems where we don't receive start/end columns:

theia/packages/task/src/node/task-abstract-line-matcher.ts

Line 204 in afd980a

range = Range.create(startLine, 1, startLine, Number.MAX_VALUE);

Number.MAX_VALUE is something like 10^308. Since Range.create always throws in this case, we never receive any matched problems from the server, and any errors are swallowed by a catch { return undefined }.

How to test

0. Use this reproducible setup:

A file named test.js in the project root:

console.log('[DUMMY] WARNING test.js:1 This is a dummy warning')
console.log('[DUMMY] ERROR test.js:2 This is a dummy error')

A task definition like this:

{
  "label": "Test Matcher",
  "type": "shell",
  "command": "node",
  "args": [
    "test.js"
  ],
  "problemMatcher": {
    "name": "test-matcher",
    "owner": "test-matcher",
    "fileLocation": [
      "relative",
      "${workspaceFolder}"
    ],
    "pattern": {
      "regexp": "^\\[[A-Z]+\\] (INFO|WARNING|ERROR) (.*):(\\d+) (.*)$",
      "severity": 1,
      "file": 2,
      "line": 3,
      "message": 4
    }
  }
}

1. Run the Test Matcher task
2. Open test.js and assert that the first line is marked with a warning
3. Assert that the second line is marked with an error

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• As a reviewer, I agree to behave in accordance with the review guidelines

[colin-grant-work]

I confirm the presence of the bug on master and the efficacy of this fix. 👍