fix(build-vscode): support VSCODE_ELECTRON_REPOSITORY/_TAG env vars in gulpfile

ppc64le/loong64/riscv64 builds use community Electron forks (lex-ibm,
darkyzhou, riscv-forks) because the official electron releases lack those
binaries. cortexide-builder's package_bin.sh exports
VSCODE_ELECTRON_REPOSITORY + VSCODE_ELECTRON_TAG and previously relied on a
.js patch step to make the gulpfile honor them — but cortexide ships
gulpfile.vscode.ts (no .js), so the patch attempt failed with ENOENT and
exited 1 for those archs.

Add native env-var support in the .ts source: when set, merge \`{ repo, tag }\`
into electronConfig before the spread that builds the @electron/get options.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: Tajudeen

build/gulpfile.vscode.ts

@@ -525,11 +525,22 @@ function packageTask(platform: string, arch: string, sourceFolderName: string, d
 			all = es.merge(all, shortcut, policyDest);
 		}
 
+		// Allow overriding the Electron repo + tag via env vars so community arch builds
+		// (ppc64le/loong64/riscv64) can pull from arch-specific forks (lex-ibm, darkyzhou,
+		// riscv-forks) instead of the official electron releases that lack those binaries.
+		const electronOverride: { repo?: string; tag?: string } = {};
+		if (process.env['VSCODE_ELECTRON_REPOSITORY']) {
+			electronOverride.repo = process.env['VSCODE_ELECTRON_REPOSITORY'];
+		}
+		if (process.env['VSCODE_ELECTRON_TAG']) {
+			electronOverride.tag = process.env['VSCODE_ELECTRON_TAG'];
+		}
 		const electronConfig = {
 			...config,
 			platform,
 			arch: arch === 'armhf' ? 'arm' : arch,
 			ffmpegChromium: false,
+			...electronOverride,
 			...(embedded ? {
 				darwinMiniAppName: embedded.nameShort,
 				darwinMiniAppDisplayName: embedded.nameLong,