chore: add publish npm action

[juleswritescode]

The publish action will be a bit different from biome's because we want to review our Releases as Drafts.

next steps:

• replicate all the relevant /packages/@pglt/* folders
• verify that downloading assets works
• make sure we can publish prelease versions
• once all that's done, we can publish to NPM

then head over to publishing for brew

[psteinroe]

great work! should we already update it to the correct names before merging or merge it now or keep it open until we have the input from supabase?

[juleswritescode]

@psteinroe this is not the most up-to-date version, I'll push that from my private branch later 👍
Regarding the name: I don't mind, we can also deploy to a different package name and delete it later. Shouldn't be a problem right now, I did that a couple of times on npm 👍

[juleswritescode]

@psteinroe Okay it's done! The package is now named pglt and the subpackages e.g. pglt-aarch64-linux.
It would be cool if you could double-check all the names and repository URLS – already it it twice, but I'm a bit tired
🤓

[psteinroe]

double checked the names and couldn't find any mismatch!