Use of relative paths in 'sh' command fails with the use of multiple dev config files

[svrana]

dev attempts to map the commands entered to their locations on the container. This is done by assuming that .dev.yaml is the root of the volume you have mapped in. This breaks down when you specify multiple config files. With multiple config files, the location of the first .dev.yaml is used even though the sh command could be running for a project in a subsquent dev yaml.