Chore: remove automated npm publishing

[katspaugh]

Automatically publishing an NPM package w/o 2FA poses a security risk, so we're disabling this.
cc @rmeissner

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[dasanra]

Instead of directly publishing wouldn't make sense to create bundled artifacts to be added to the release in some .zip that could be later on uploaded to npm with all security measures? Instead having to bundle again in local computer without the guarantee of bundling the expected version

[katspaugh]

I personally don't mind building locally but it could be an option.

[dasanra]

For me this would minimize other issues like using the wrong commit or forgetting to run npm install before bundling it locally again. I think this is one important value of CI automated systems

[katspaugh]

I agree, it could be more robust. Could be a future improvement. Can we merge this PR as is though, for now?
The API key won't work anymore after Richard's changes.