Request for more verbose erroring on `bootc container lint`

Edit: The issue is a filesystem configuration error on Zirconium's end. I've amended this issue, as the error output from `bootc container lint` was not at *all* clear as to which path was causing issues.

The issue here is that `bootc container lint`, when faced with a path that leads outside of the filesystem, errors out without telling you which path is causing the problem. Adding `RUST_LOG=debug` or even `RUST_LOG=trace` does not help here. It's still not verbose enough on this particular step of linting. It would be nice to at least show the path that it errored out on.

Old description text:

I'm running into this on [zirconium-hawaii](https://github.com/zirconium-dev/zirconium-hawaii) testing images, but I can also reproduce this on images for [Zirconium (fedora)](https://github.com/zirconium-dev/zirconium). Ever since bootc 1.16.11, `bootc container lint` has been failing with the error `error: Linting: Unexpected runtime error running lint runtime-deps: a path led outside of the filesystem`. I've attached screenshots with RUST_LOG=debug enabled, but it doesn't seem to provide me any useful information.

I think the problematic commit is https://github.com/bootc-dev/bootc/commit/98bc78d441bc620201b598e44db88e28c8640d10. I've tested this on the bottom-most screenshot.

zirconium:latest (Fedora 44), running `bootc container lint` on commit https://github.com/bootc-dev/bootc/commit/98bc78d441bc620201b598e44db88e28c8640d10 and https://github.com/bootc-dev/bootc/commit/3324be45d578beb0c09e5ed717963fa8bbe5cf4e respectively.

Reproduce the failure with `bootc container lint` on the Zirconium images and compare the referenced commits 98bc78d441bc620201b598e44db88e28c8640d10 and 3324be45d578beb0c09e5ed717963fa8bbe5cf4e. Trace the lint step that reports a path outside the filesystem; done means the error identifies the path that caused the failure.

Written by the indexing model from the issue text.