typescript bindings maintenance

[iimez]

Describe your changes

• Changed the build scripts and docs a bit so its easier to build the bindings from source.
• Deleted some outdated comments from the gyp config, and removed the deprecated nCtx on completions.
• Update the build_unix script to produce so files with the correct build type.
• Changed CI to call cmake with Release build type.
• Added support for streamed token decoding, following the python bindings implementation
• Updated the bindings to expose additional LLModel:load and LLModel:initGpu methods so its easier to copy the loading and backend-picking logic of the CUDA Backend PR. I also renamed a few things for consistency.
• Include nThreads in the LoadModelOptions, previously it had to be configured via setThreadCount.
• Added nGpuLayers as alias for ngl to the LoadModelOptions.
• Updated types and examples accordingly.
• I added a test suite that does actual inference and loads a real model on both cpu and gpu with minimal resource usage. And moved the existing tests into a separate test:ci script. Can switch CI config back to yarn test if inference in CI is possible.
• Updated deps and verified that the fallback node-addon build via node-gyp-build is still working. Changed the build setup a bit to include a assert-backend-sources.js script that facilitates easier testing of the fallback during development. This also allows us to get rid of the second bindings.gyp config.

Breaking changes

• The CompletionOptions onReponseToken(tokenId, text) callback has been changed to onResponseTokens({ tokenIds, text }) (Note the plural.). This is related to the streamed emoji decoding / multi token character issue.

Issue ticket number and link

#2326

[jacoobes]

could this be a usecase for fs.mkdir(sourcePath, { recursive: true })?

[iimez]

Not what we want here I think, because when the script gets executed by the user during the install hook (ie user installs the package as a dependency) this would create a gpt4all-backend path under node_modules. And then error because there are no gpt4all-backend sources under that newly created dir. We really just want it to do nothing in that case.