feat: add package scripts for Debian and Alpine

[edubart]

This PR contains hardlinks to https://edubart.github.io/linux-packages in many places, where I am personally temporary hosting packages using GitHub pages, the idea is to change this to official cartesi URL once when have official distribution repository.

Building

There is no CI workflow set up, you can build all packages locally with:

make -C alpine
make -C debian

This will use Docker to build packages for amd64/arm64/riscv64 for both Alpine/Debian without any cross compilaton, this may take hours, please do not use make -j$(nproc) to speed up, this is not supported at the moment and may mess the package registry. Once done Debian/Ubuntu packages will be available in the cdn/apt directory, and Alpine packages in cdn/apk directory. The idea of cdn directory is to copy and host it in a HTTPS web server, at the moment I am temporarily hosting in a separate repository using GitHub Pages.

The first time you execute make it will automatically generate private signature keys in alpine/key and debian/key. This keys should be kept private. Debian uses GPG keys, while Alpine uses customized OpenSSL keys.

Typing make subsequent times will only build packages if its build script is newer than the ones found in package archive cdn.

Testing locally

After all packages are build, assuming cdn directory is filled with the package registry, you can test installing all of them locally with:

make -C alpine test
make -C debian test

This test will also execute some of the packages to check if it's indeed working, for instance it execute cartesi-machine command for amd64/arm64/riscv64 to check if it can boot its guest Linux system.

Testing remotely

The README of Alpine/Debian contains instructions on how to use remote repository in both host or guest environments, you can manually follow the instructions in a brand new Docker image shell to check if the remote repository is working.