The .pipe() method on Node.js streams have a gotcha in that they
do not propagate errors downstream. In this case this meant that if
compilation failed with an error, it 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 changes a few uses of .pipe() to the more modern stream.pipeline(),
which propagates errors correctly.

Avoid unhandled errors in build streams

Add `.github/actions` as a folder to include. The folder doesn't exist at the moment, but it may in the future.

Update codeql-config.yml

Bump CLI Version to v2.21.1 for integration tests

Pin azure/login Action