Fix build, add lock file, upgrade GitHub Actions

[thomastoye]

Hi @epoberezkin, I've fixed the build, upgraded GitHub Actions to the latest version, dropped old Node versions and added 16.x and 18.x, and added a lock file to prevent the build from breaking due to in-range update breakage.

Let me know if this looks good. I'd like to add ESM output in a subsequent PR.

[G-Rath]

Looks good to me - fwiw I think it's probably worth just typing the errors as any for now rather than casting; ideally we should also have an .npmignore that excludes the package-lock.json

[epoberezkin]

I think recommendation is to use lock files only in applications, but not in the libraries.

[G-Rath]

The general opinion is pretty divided - fwiw I say you should always commit your lockfiles, because you can always have CI workflows for libraries that remove them in order to test that everything works with the latest versions while still retaining the lockfile to prevent issues like this from breaking the general development flow.