This matches the behaviour of the Chromium OS ebuild for this package:
https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/cd6d6815b1604105cb6b8c40b2e0c3f15f401e3b/chromeos-base/minijail/minijail-10-r38.ebuild#47

…ayers so it can exclude the top-most level

Before, every docker image had three extra layers:

1. A `closure` layer which is an internal implementation detail of
   calculating the closure of the container
2. a `name-config.json` layer which is the images' run-time
   configuration, and has no business being *in* the image as a layer.
3. a "bulk-layers" layer which is again and implementation detail
   around collecting the image's closure.

None of these layers need to be in the final product.

Without changing behavior, since this code is fiddly, make it possible
to add a filtering step before packaging individual paths.

…l layers

Otherwise it cannot log in to new workspaces.

kubernetes-helm: Add shell completion

cups-dymo: fix build

minijail: install .pc files and scoped_minijail.h

…ion-detail-layers

dockertools.buildLayeredImage: remove implementation detail layers

slack: add xdg_utils to the PATH