Including full error range in TSC output

From https://github.com/Microsoft/vscode/issues/70465

Repo

1. For the TS code with strict enabled:

   const obj = {
       prop: Date.now() ? 'str' : undefined
   }
   
   obj.prop.toLowerCase();
   

2. Run a tsc task in VS Code to see reported errors (make sure to close the ts file as well)

Problem
We currently only report the potential undefined access error on obj in the line obj.prop.toLowerCase();. The correct range should span obj.prop.

The root cause of this is that VS Code's problem matcher does not have the full range of the error from tsc, only the start line and column. Here's the tsc output:

src/index.ts:7:1 - error TS2532: Object is possibly 'undefined'.

7 obj.prop.toLowerCase();
  ~~~~~~~~

With the current tsc output, there is also no way to extract the full range of the error.

Request
Somewhere in the line src/index.ts:7:1 - error TS2532: Object is possibly 'undefined'. , add the end position as well so that tooling can properly highlight it. We would want to do this in a way that doesn't detract from the error's human readability. This needs some thought

Reproduce the issue with the provided strict TypeScript example and inspect the tsc diagnostic output for TS2532. Determine how to include the diagnostic end position without reducing human readability; done means tooling can extract the full range and the existing error remains understandable.