Publish prebuilds to npm

[DeMoorJasper]

This PR switches to using prebuildify and publishes prebuilds on npm as well as GitHub, this reduces the need to run install scripts and to have an internet connection to install this package

Closes #30
Closes #26

[height]

Link Height tasks by mentioning a task ID in the pull request title or description, commit messages, or comments.

You can also use "Close T-X" to automatically close a task when the pull request is merged.

[mischnic]

I barely know how this works

I guess after the source-map endeavour, you know this better than I do 😄

[DeMoorJasper]

Not entirely sure why CI is failing, will have look at it at some point if I don't forget

[mischnic]

The Node servers are currently not working correctly: nodejs/node#32683

[DeMoorJasper]

@mischnic thanks for looking that up, would've expected azure to have a cache/proxy for things like that but apparently not

[devongovett]

Why do we need to publish the artifacts if we're not on a release tag?

[DeMoorJasper]

we don't have to, just seemed useful to always store it in azure devops in case we want to download the prebuilds and test it or something

[devongovett]

oh ok, sure.