Implement more sophisticated CI/CD strategy

[johnnyfleet]

This repo itself doesn't contain much fancy logic - all the smart work is done on (bliss.hq)[http://www.bliss.hq] itself.

I want to introduce a more sophisticated CI/CD mechanism that looks after the merging of base OS and latest versions of Blisshq.

A good example to get inspiration from is https://github.com/hertzg/rtl_433_docker.

Some ideas of what I would like:

Support a few versions of BaseOS e.g. deban, alpine.
Build for the last 10 versions of the software - allowing some backward compatibility.
Each week build and push the latest versions of those base images - taking care of ongoing maintenance automatically.
Take care of version bumping everything and tagging everything.

Only when I make an adjustment to the dockerfile (this repo) - do something more sophisticated. What exactly is TBD.