fix: npm publish issue with glib

[ologbonowiwi]

• build: add libc to generated package.json
• refactor: delete post-install script

Summary:
Replacing post-install script by libc field on package.json (which is handled automatically by Node.js)

Issue Reference(s):
Fixes #628

Build & Testing:

• I ran cargo test successfully.
• I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

• I have performed a self-review of my own code.

[neo773]

This might get problematic as support for libc field landed quite recently in npm@9.6.5

We'll also have to account for third party package managers like yarn and pnpm

[ologbonowiwi]

I know that yarn, pnpm and bun already supports, but I didn't knew about the version restriction on NPM.

maybe we should close this @meskill?

[meskill]

This might get problematic as support for libc field landed quite recently in npm@9.6.5

We'll also have to account for third party package managers like yarn and pnpm

there is already npm@10 and the v9 is shipped with the node18 that soon will enter maintence stage. So, we could actually just support those active versions for npm and probably for other package managers as well.

I suggest also to take a look into swc repo and issues and search for any issues they have with libc field as I saw they are using this approach