[CI] Improve npm publishing

[nebula-aac]

Currently we're using changeset to initiate the publish, however some of the process is still manual.

Research ways to improve this.

What is supposed to happen is that with the current GitHub Action workflow, anytime there is a PR that is merged into the repo, the job changesets is supposed to be ran to build and publish the packages.

However the last merge, published packages that was already done.

Need to research a bit more on the process as we do need another release at this time.

---

Contributor Guides and Resources

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
• 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

[nebula-aac]

#65