Nested volume mounting behaviour is not compatible with Docker

[ningziwen]

Describe the bug
There appears to be a behavior mismatch between Finch and Docker in the handling of nested volume mounts. In Docker, a nested volume within another volume is correctly accessible, while in finch, the same nested volume fails to be accessible and returns an error "No such file or directory".

Steps to reproduce

finch run --rm -it -v /tmp/test-1/test-2:/test-1/test-2 -v /tmp/test-empty:/test-1 public.ecr.aws/amazonlinux/amazonlinux:2 bash

In bash,

ls /test-1/test-2

The 'ls' command results in the following error:

ls: cannot access /test-1/test-2: No such file or directory

Expected behavior

In Docker, it can return the correct content under test-2. The compatibility with docker is expected.

Additional context
Nerdctl issue: containerd/nerdctl#2254

To help debug the issue as quickly as possible, we recommend generating a support bundle with finch support-bundle-generate and attaching it to this issue. This packages all Finch-related configs and logs into one file.

[ningziwen]

In parallel of working on the fix in Nerdctl, trying to make a temporary fix change under FINCH_DOCKER_COMPAT env var to help Finch users unblock themselves immediately.
#417

[ningziwen]

The fix in Nerdctl is merged. containerd/nerdctl#2255