Use Github Actions for release automation about js-test

[Timecraft]

Confirmed the necessity to update appdata.xml by Daniel

Edit note: brackets then parenthesis for links dang it ;-;

[Timecraft]

A release automation workflow is in the repository, but it relies on branch juno to have a pull request to run. The juno branch will be the "stable" branch, and will be updated by pull requesting from master whenever it is time to release a new version. This will require updates to appdata.xml, as mentioned above, but should automate the updates to the debian files, which is a huge help.

[Timecraft]

Keeping this issue open until we confirm that the automation works

[Timecraft]

The version of the release automation that elementary provides requires a launchpad account. There's possibility that I could create my own version of a release automation that uses GitHub hub instead.

[Timecraft]

Even though the latest test in release automation (and the huge amounts of fumbling about by me) ended in a failure, the failure was due to the dummy package having a version tag of v0.0.0, which is less than v0.1.0. That means it is working