chore: speedup builds for binary and prepackage

[uinstinct]

Description

Using child processes and parallel executions, this PR accelerates installations, copying and downloads. In most cases, the performance improvement is more than 2x.

• put installNodeModuleInTempDirAndCopyToCurrent into install-copy-nodemodule.js for copying lancedb targets on parallel in child process
• install node modules for gui and vscode on parallel using child process npm-install.js
• install and copy sqlite and esbuild on parallel using child process download-copy-sqlite-esbuild.js
• bundle binaries and download sqlite and ripgrep in parallel in child processes bundle-binary.js
• used nodejs http dowload over curl (http is 2-3x faster than curl)
• generate and copy config yaml schema in a child process so that npm installations can be done on parallel generate-copy-config.js
• refactoring of few functions to avoid duplication
• when running "launch extension" using the vscode debug panel, prepackage will skip installing and downloading dependencies

performance improvements from my machine:

	previous	now
npm run build (binary)	65 seconds	15 seconds
npm run prepackage (extension/vscode)	22 seconds	10 seconds
install dependencies script	139 seconds	88 seconds

CON-2267

Checklist

• [] I've read the contributing guide
• [] The relevant docs, if any, have been updated or created
• [] The relevant tests, if any, have been updated or created

Screenshots

[ For visual changes, include screenshots. Screen recordings are particularly helpful, and appreciated! ]

Tests

[ What tests were added or updated to ensure the changes work as expected? ]

[cubic-dev-ai]

Your cubic subscription is currently inactive. Please reactivate your subscription to receive AI reviews and use cubic.

[netlify]

👷 Deploy request for continuedev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	01930c9

[recurseml]

⚠️ Only 5 files will be analyzed due to processing limits.

[recurseml]

In the copySqlite function, the promise is resolved unconditionally after the error check. If msg.error is true, the code will still call resolve() right after calling reject(), leading to an inconsistent promise state. The resolve() call should be in an else block to ensure mutual exclusion with the error case.

---

React with 👍 to tell me that this comment was useful, or 👎 if not (and I'll stop posting more comments like this in the future)

[recurseml]

Similar to the copySqlite function, the copyEsbuild function has the same promise resolution issue where resolve() is called unconditionally after the error check. The resolve() call should be in an else block to prevent resolving after an error has occurred.

---

React with 👍 to tell me that this comment was useful, or 👎 if not (and I'll stop posting more comments like this in the future)

[recurseml]

😱 Found 2 issues. Time to roll up your sleeves! 😱

[uinstinct]

normal.extension.launch.mp4

faster.extension.launch.mp4