multicall binary? #151
Description
Most of the size of voorkant-lvgl, besides fonts, is libraries we use. voorkant-cli then also has at least one of those libraries (curl). Shipping both binaries as static builds for a system wastes 'one curl' of space. If we instead have our build always generate exactly one binary, that may or may not have LVGL support, may or may not have FTXUI, and perhaps always has the bits from -cli (which are basically free once the libs are in!), we avoid this overhead.
Given how few users we have right now, we don't even really need symlinks to make the 'old' names work, and we can just start calling the binary voorkant.