Avoid unhandled errors in build streams

[asgerf]

The .pipe() method on Node.js streams have a gotcha in that they do not propagate errors downstream. This PR changes a few uses of .pipe() in our build scripts to the more modern stream.pipeline(), which propagates errors correctly.

Previously, if compilation failed with an error, the error would not be visible to Gulp because Gulp only sees the stream that writes to a file, not the intermediate 'esbuild' stream that generated the error. This resulted in unhelpful errors of the form:

[13:56:21] The following tasks did not complete: default, <series>, <parallel>, compileViewEsbuild
Did you forget to signal async completion?`

Now that the errors is propagated correctly, the TypeScript build error is surfaced correctly. In my concrete case this became the build error

[13:58:54] 'compileViewEsbuild' errored after 410 ms
[13:58:54] Error in plugin "gulp-esbuild"
Message:
    Build failed with 1 error:
src/view/compare-performance/ComparePerformance.tsx:24:27: ERROR: Could not resolve "crypto"

[Copilot]

Pull Request Overview

This PR updates our build scripts to use the modern stream.pipeline() API instead of .pipe() so that errors from intermediate build streams are propagated correctly. Key changes include:

• Replacing .pipe() chains with pipeline() calls in view.ts, typescript.ts, and textmate.ts.
• Updating the import of pipeline from stream/promises for each file.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
extensions/ql-vscode/gulpfile.ts/view.ts	Replaces .pipe() usage with pipeline() in compileViewEsbuild
extensions/ql-vscode/gulpfile.ts/typescript.ts	Updates compileEsbuild to use pipeline() instead of chained .pipe()
extensions/ql-vscode/gulpfile.ts/textmate.ts	Implements pipeline() in compileTextMateGrammar for proper error handling

[aeisenberg]

Nice.