Warden should use physical vs logical working dictory with docker-compose

[davidalger]

Docker for Desktop v2.2.0.0 changed the way File Sharing paths can be specified and no longer allows entering a path manually. Using the file browser to select a directory to share a symlinked location resolves the symlink, making it thus impossible to share a location using the symlinked path.

This change in docker causes problems when using /sites/exampleproject to run warden env ... commands and where /sites is a symlink resolving to (for example) /Volumes/Server/sites.

Resolution to this should be simple changing use of pwd to pwd -P in order to enforce uniform use of the physical location.

Effects of this change

a) Output of warden env config will use physical paths in volume mount points as docker-compose will be executed using the physical path of (based on example above) of /Volumes/Server/sites/exampleproject rather than /sites/exampleproject

b) Users with only /sites exported in File Sharing preferences will need to share the correct physical location of /Volumes/Server/sites instead

c) It will no longer matter which working directory warden is run from (i.e. /sites vs /Volumes/Server/sites) as they both will operate identically (using the latter of the two in this case)

Example from File Sharing preferences in new Docker Desktop version: