Use custom node-gyp for SDL pipeline

[rzhao271]

No description provided.

[rzhao271]

The VS Code Scan failed due to Binskim, which is currently being resolved elsewhere.
What is relevant for the scan results is that the dependencies are being installed and compiled properly.

[rzhao271]

Building the custom node-gyp is still good, so the CI passes those steps, but it fails in general because it's missing symbols, still.
CI run: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=210534&view=results

We can merge this PR in and wait for the symbols, or we can wait for the symbols first.

[deepak1556]

Lets wait for the pdb files and get a green CI before merging.

[deepak1556]

Pdb are now available starting with https://github.com/microsoft/vscode-electron-prebuilt/releases/tag/22.4.5, please rebase on top of main once #179857 gets merged.

[rzhao271]

Symbols are still not being downloaded. Looks like the scan gulp file might be a bit broken. Investigating.

[rzhao271]

This took me way too long to figure out.
Upstream PR: joaomoreno/gulp-atom-electron#80

[deepak1556]

👏 spectre flag is only raised for Electron related binaries and keytar as expected.

I am good with the changes of this PR but lets wait for @joaomoreno who will be back on Monday and we can get a new version of gulp-atom-electron and we can switch to it instead.

[rzhao271]

We're now using @vscode/gulp-electron!
The SDL scan continues to pass with keytar.node marked as the only native node module without Spectre mitigation added.

SDL scan: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=211604&view=results
Raw Binskim log for that scan: https://dev.azure.com/monacotools/a6d41577-0fa3-498e-af22-257312ff0545/_apis/build/builds/211604/logs/55