feat: Handle disabled install scripts

[timfish]

npm is changing the default to no longer run install script.

This PR moves the install script logic into the side-effects of loading the module. Things become a little more complex because this library is loaded from multiple threads so we have to lock the rebuilding so it only runs once. It's tricky to do if you want to be able to recover from all the possbible failures states!

I had to inlcude a dummy install script otherwise npm and yarn v1 automatically run node-gyp rebuild at install time!

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3f5c888. Configure here.}

[JPeer264]

There is now quite some acrobatics needed 😅

[JPeer264]

q/l: Is it on purpose only testing for node 18 and 26?

[timfish]

Yes, didn't want to add all of them and testing oldest and newest should be enough...

[JPeer264]

Unnecessary byte saving suggestion

Suggested change

	exportconstidentifier=[platform,arch,stdlib,abi].filter(c=>c!==undefined&&c!==null).join('-');
	exportconstidentifier=[platform,arch,stdlib,abi].filter(c=>c!=null).join('-');

[JPeer264]

m/h: The node engines are ^18.17.0 || >=20.5.0 based on this. Not sure if this is satisfying our supported engines I'm afraid. v10 would work though, not sure if this can be considered 🤔

[timfish]

Closing in favour of doing something less complex!