Setup CI/CD pipeline for NPM publish

[cairocoder01]

Currently, you just run npm publish --access public in the root of the site and it will publish.

The pipeline should do the following:

• Run eslint
• Run tests
• Build dist folder (npm run build)
• Should it build the localize js files?
• Publish to NPM (npm publish --access public)

[micahmills]

The translation system for the theme and plugins is changing in the coming weeks. I think we should try to integrate with that as much as possible so we can probably hold off on the localize stuff until the dust has settled on the new process.

[cairocoder01]

This is setup for the basic build and publish action. I'll leave this issue incomplete as a reminder that we'll still need to integrate the localization process.