The working directory of service containers is not respected

[jheino]

If a Drone pipeline has a services section, the service containers within are started with the working directory set to the Drone workspace (i.e. /tmp/aws/drone/src) when using the AWS runner. This is different from the Docker runner which retains the working directory set by a WORKDIR statement in the Dockerfile.

AWS runner overriding the working directory for services is problematic because some services/containers may depend on being started inside a specific directory. At the very least, the behaviour should be documented and consistent with other types of runners. There is an undocumented(?) setting working_dir which AFAIU should allow the user to override the directory, but the setting doesn't do anything when the AWS runner is used.