Adding automated build & tag update on release

[robzr]

Summary

As identified in #16, there are no automated builds or releases being done. This added workflow will build on release and update the associated major/minor tracking tags - if you do a v1.16.0 release; it will build, update the dist/index.json to a new commit, then update the release tag as well as the tracking tags v1 and v1.16 automatically.

It will still require someone manually making a new version release after a merge to master. This could further be automated to use a merge commit message.

Requirements (place an x in each [ ])

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[CLAassistant]

All committers have signed the CLA.

[m5kr1pka]

@stevengill maybe Google's automated Release Please Action would be a more appropriate approach for an enterprise level action with Conventional Commit Messages.

[robzr]

@stevengill maybe Google's automated Release Please Action would be a more appropriate approach for an enterprise level action with Conventional Commit Messages.

Right now there is no CI building, and the last merge to master wasn't built or released, so this at least fixes that.

release-please-action looks interesting, but it is an opinionated flow that would require all contributors to buy into "CCM", so that's a cultural change.

[stevengill]

This is great! Thank you!!