Use working_dir in generated docker-compose instead of dynamically setting working_dir on launch

[mstrelan]

I've been following along with #3130 and https://drupalize.me/blog/debug-any-drupals-phpunit-tests-phpstorm-ddev-local-environment but ran in to an issue when running Drupal Test Traits.

When phpstorm runs the test via docker exec it runs from / instead of /var/www/html and therefore DrupalFinder can't find Drupal. This is because the working directory is dynamically added to the ddev exec commands. Would it be possible to add the working_dir to the docker-compose file instead or as well?

To get around the issue for now I'm adding a custom docker compose file to set this:

.ddev/docker-compose.env.yml:

version: '3.6'
services:
  web:
    # This makes sure the working dir is set for running tests via phpstorm
    working_dir: /var/www/html

[rfay]

I accidentally worked on this and would love to have you review it @mstrelan - You can use the gitpod links in #3160 or download the artifacts from https://github.com/drud/ddev/actions/runs/1126173412

[mstrelan]

I tested this out today and it worked great, thanks again!