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?

Start at the install-to-filesystem command entry point and trace how the target OS, filesystem, and storage configuration are identified. Define a sanity check for required target-kernel support, including the btrfs and LVM cases described here; done means incompatible targets are detected or clearly reported before installation.

Vom Indexierungsmodell aus dem Issue-Text verfasst.