chore(core) publish NPM packages from CI

[chrisgervang]

Background

Aligned with visgl/deck.gl#8828

After this PR, the publish workflow will be

• Switch to the appropriate branch (master for alpha/beta in development or *-release for production)
• Edit CHANGELOG.md
• Run yarn publish-beta or yarn publish-prod (note: with dash)

The publish command will only bump versions in package.json files, tag the commit and push to remote. The CI will then test, build, and publish to NPM.

As discussed offline, this will remove the differences in local dev environments and ensure predictable results. Also saves us time from working around render test inconsistencies and random errors.

I have tested the version bumping and tagging part of the workflow. Can't verify the CI workflow until merged. May need to follow up with more PRs to fix any CI issues.

Change List

• Bump ocular-dev-tools
• Enforce changelog update before publishing
• Release CI flow

Change List (outside this PR)

• Add npm access token as secret
• Restrict push permission of *-release branches to admins only

[coveralls]

Pull Request Test Coverage Report for Build 9195943884

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 55.533%

---

Totals
Change from base Build 9183175190:	0.0%
Covered Lines:	1557
Relevant Lines:	2851

---

💛 - Coveralls