Improve version release method

[jameshadfield]

context

Currently we use a custom script (./releaseNewVersion.sh) to release new versions of auspice which could be much simplified, and is constrained in its versitility (e.g. one can't release alpha/beta versions). It also uses a separate release branch which seems unnecessary since we use tags for each version release.

Suggested release mechanism

Should be as simple as

• update changelog
• npm version ... (has the benefit of updating package-lock.json, which we aren't currently doing)
• git push
• Publish to NPM. Currently this is done by travisCI from the release branch. Could be done manually via npm publish [--tag beta] or via GitHub actions / travisCI.
• Rebuild docker image (same as above)

[jameshadfield]

This issue is well out of date now. While we can (and should!) improve the release process, #1777 is the best target for now