Add Node.js prebuilds to language grammars

[segevfiner]

Problem

Having prebuilds is useful as you then don't have to have a compiler to use them, and can use the prebuilds to generate distributions for different operating systems without having to do so on each target operating system due to having to compile binaries.

This can be done by providing a GitHub Actions workflow, possibly generated by the cli generate command and appropriate config/scripts to be included in the package.json.

This will be easier if we migrate to napi as then we will only really need one binary per OS/arch combination rather than also for each major version of Node.js.

Expected behavior

For language grammar for Node to have prebuilds.

[ObserverOfTime]

I tried that for tree-sitter-cli in ObserverOfTime@d1eace2 but the package would be too large.
Although, parser libraries should be considerably smaller so it might be doable for those.

[segevfiner]

I meant using prebuild/prebuild-install, like already used in node-tree-sitter. This won't make the package larger as it downloads prebuilds from a GitHub release.

[segevfiner]

Continuing on from #3106 (comment), if we want to use prebuildify instead of prebuild.

• The workflows are not generated by default by generate so how are language authors supposed to know about them?
• Do we want our own prebuildify workflow or is there any workflow/action that we can reuse?
• Not using node-gyp-build is troublesome, as you need to for the install command for unsupported targets, and the logic to import the right addon module is quite a bit more complex with prebuildify than with prebuild.

[segevfiner]

Anyhow, this is an example of adding prebuild: segevfiner/tree-sitter-hello@main...prebuild
And this one is an example of adding prebuildify: segevfiner/tree-sitter-hello@main...prebuildify

Let me know which one you want to turn into a PR. And whether you want to do something about what I wrote above. e.g. To let users know where the shared workflows are.

@amaanq @ObserverOfTime @verhovsky

[ObserverOfTime]

The workflows are not generated by default by generate so how are language authors supposed to know about them?

The workflows are still subject to change but a reference in the docs would be nice to have.
Alternatively, there's a (not entirely official) template that includes them.

Do we want our own prebuildify workflow or is there any workflow/action that we can reuse?

I will update the package-npm workflow accordingly.

Let me know which one you want to turn into a PR.

prebuildify is definitely the better option.
I can add it to #3126 which has a few more npm stuff.