Create separate top files for opt-in components

[scjudd]

For example, not everyone is going to be running from a Librem 14, so those states should not automatically be applied.

In the Salt documentation for Qubes, there is a section on enabling additional top files. What we could do is create a librem-14.top file, for example, and then users having a Librem 14 machine could enable this top file like so:

# qubesctl top.enable librem-14

The user-config state is another good example. That one is a mix of generally useful configuration (i.e., GPG SSH agent support), but is currently intertwined with my own git and vim configuration, which are obviously only desirable to me. I think the latter should probably be broken out into another repo, but would still likely use the qubesctl top.enable functionality.

[scjudd]

Just broke out librem-14 into its own top file and pushed that up. It works as described above. Need to think a bit on how this works for things like user-config, fonts and desktop, which may not necessarily match anyone else's preferences. I'm thinking this may require breaking things into separate repositories, which may be cloned to different subdirectories under /srv and layered on via qubesctl top.enable. 🤷