store: Don't use CONSUME flag

libostree currently has a bug here with fsverity support;
in the consume case (which right now is always zero-sized
files because we don't hardlink them) it doesn't enable verity.

This would be an easy bug to fix in libostree.

But OTOH there's no real reason to set consume here either.
The main idea of consume is when one is operating on potentially
large files external to libostree, but most things here are
hardlinked, and what isn't is just the zero sized files.

Signed-off-by: Colin Walters <[email protected]>

Author: cgwalters

ostree-ext/src/container/store.rs

@@ -1058,7 +1058,7 @@ impl ImageImporter {
                 let root_dir = td.open_dir(rootpath)?;
 
                 let modifier =
-                    ostree::RepoCommitModifier::new(ostree::RepoCommitModifierFlags::CONSUME, None);
+                    ostree::RepoCommitModifier::new(ostree::RepoCommitModifierFlags::empty(), None);
                 modifier.set_devino_cache(&devino);
                 // If we have derived layers, then we need to handle the case where
                 // the derived layers include custom policy. Just relabel everything