Improve local debugging of e2e tests

[bashir2]

I have been trying to debug an e2e failure that I cannot explain (context: PR #254) hence tried steps described here to run the tests locally. Running the cloud-build tool locally, it gave me a new error that does not happen on the non-local version (pasted the error at the end). I have not got to the root cause of this but it took me a while to find a workaround by adding the full-path here. Note this error does not happen when running openmrs-compose.yaml through docker-compose either so it is unique to the cloud-build in local mode.

In general, debugging e2e failures locally is not a great experience right now. For example, we should have a way to easily bring up and leave some services like openmrs and hapi (instead of rerunning them everytime) and skip some steps that are not needed for a particular problem for quick retries of the problematic part.

Here is the aforementioned error for reference:

ERROR: for openmrs-fhir-mysql  Cannot start service mysql: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:59: mo
unting "/workspace/docker/mysql-build/mysqld.cnf" to rootfs at "/var/lib/docker/overlay2/68f879715466e9256b46dfc302c2328fd8777a4abebba14ccb5f90412e4bc54f/merged/etc/mysql/mysql.conf.d/mysqld.cnf" caused: not a directory: unknown: Are you trying to mount a di
rectory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

[bashir2]

@omarismail94 FYI