consider some way to verify target OS compatibility with `install-to-filesystem`

I got caught out with using `install-to-filesystem --replace=alongside` against a Fedora Cloud instance (using btrfs) when targeting Fedora ELN (doesn't enable btrfs).

This problem generalizes to things like installing to LVM but not having LVM in the container, etc.

This is quite tricky to test, but I think we could at least do a dirty sanity check for having the kmod in the target kernel or so?