chore: add libc field to node packages

[paul-soporan]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

This PR adds a libc field to the relevant Node packages.

Originally introduced by Yarn 3.2 (yarnpkg/berry#3981), the field is the equivalent of os / cpu but for libc (currently supports glibc & musl). It allows package managers to skip installing packages with incompatible libcs.

It has since been implemented in pnpm (pnpm/pnpm#4454) and cnpm (cnpm/npminstall#387), and npm has plans to implement it too (npm/rfcs#438).

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
• I have added a convincing reason for adding this feature, if necessary

Other information

[lucasfernog]

Amazing, thank you!