Revisit linting, testing, code coverage, and package publishing plans

[ibnesayeed]

Over the time we have tried many different tools, packages, and services for linting, testing, and code coverage etc. As a result there are some files, dependencies, and configurations who's presence is unclear or confusing.

Linting

• Do we want to continue using existing Python and JavaScript linters or should we update any of that?

Testing

• Which testing framework do we want to use and what configurations do we want when running those tests?
• Remove any unnecessary files and dependencies and update dependencies to their latest versions.
• Which CI platforms do we want to use: Travis CI, GH Workflows, or both?

Code Coverage

• Do we want to run local tools for code coverage, a service, or both?
• If we do choose to use a service, do we want to use their GitHub App (with more access) or incorporate their GH Action?

Publishing

• Should we use GH Workflows to build and push releases to PyPI or let PyPI pull our code and package them on their servers (this has consequences of the origin of credentials/access tokens)?
• Should we let DockerHub auto-build images by pulling our code (which is taking longer these days and the automation is broken and it requires access to an entire GH account) or let images be built in GH Workflows and push them to DockerHub (this has consequences of the origin of credentials/access tokens)?
• Do we also want to release packages in GH Package Registry?