Automate publishing process to avoid issues

[giordano]

Feels like all the instructions in that file should be a dispatch workflow so that you click a button and everything is done automatically.

Originally posted by @giordano in #278 (comment)

[DilumAluthge]

Alternate proposal:

1. Switch to the master branch of this repo being deployable (i.e. dist/index.js is checked into the repo on the master branch).
2. Then, to make a new release of this repo, you just go to the Releases tab, and create a new release off of the latest commit on master.
3. Also, remove the version field from package.json and package-lock.json.

An added benefit of the above approach is that all PR branches will become usable, so if someone wants to try out a PR before it is merge, you just point to the PR branch.