Fixes for live ISO images

[ghost]

Some small fixes to close #14.

• Disable systemd-oomd (see systemd-resolved and systemd-oomd fail in the live ISO #187)
• Remove eos-enable-zram (by updating eos-boot-helper)
• Fix systemd-resolved startup (by updating eos-bot-helper)

Tested an ISO built from these changes, and didn't see any failures except those we already see in the regular disk image. Those are tracked in #146 and #84.

Fixes #187

Part of #84

[dsd]

Is there a way for things like elements/eos/eos-boot-helper.bst to just track the latest version automatically? That would make it more equivalent to the eos6 CI setup we were using before.

[ghost]

Is there a way for things like elements/eos/eos-boot-helper.bst to just track the latest version automatically? That would make it more equivalent to the eos6 CI setup we were using before.

Yes, there are two ways to do this.

One is to simply set ref: master, so every time you run a build you get the latest version. While that sounds great, every time I've set up a project that way I've ultimately regretted doing so because of the unpredictability it introduces.

(E.g. you might be working on a change on a feature branch of eos-build-meta; someone merges a bad change in eos-boot-helper, and your feature branch immediately breaks. At this point, if you're anything like me, you think "I did somethink wrong in my branch" and lose time to a bunch of unnecessary debugging).

The other is to set up an "auto update" bot which runs on a timer, runs bst source track on elements you choose, and opens PRs against eos-build-meta each time there's a change upstream. Freedesktop SDK and GNOME OS both do it this way and it shouldn't be too hard to re-use their automation. Perhaps you'd need to add Github support as they are both Gitlab based.