ClarionSOS + Arch + Arm

[faddat]

So I've got this lil thing:

https://github.com/faddat/sos

I use it in Blurt's CI system to make these images:

https://megadrive.blurt.world

• First I'm going to get clarion rolling in docker on my graviton instance. Can observe it in the github actions over at https://github.com/faddat/sos/actions
• Second I'm going contribute a build system over here that will pump out Raspbery Pi images

[faddat]

This is going to result in a number of things, it seems.

1. multiplatfrom Arch linux images that run Clarion based on the image lopsided/archlinux
2. automated ARM builds:

@bytemaster can we get a graviton instance?

https://aws.amazon.com/ec2/graviton/

That is what I use for SOS and it is wonderful.

3. Lil .img files that boot to Clarion when booted on an rpi 4 or odroid c2: more devices "Coming Soon(TM)"

4. A refactored build that builds a container, instead of building in the sparkplug0025/clarion container.

Clarion should be a device, an object.

In general, I think that it's best to have a build.yml or such that fully builds the project from source, including the installation of dependencies. This way, it is always clear how to do so in the future. Not always easy to do though, and I figure that should be considered more of a stretch item.