Fix gate scripts for local setup

* when remote_work_dir is set, document pull happens from the
  remote_work_dir (/tmp/airship) with a folder created within
  remote_work_dir with repo name (/tmp/airship/airshipctl).
  However the manifest yamls of kind "Clusterctl"
  refers to a relative path from work_dir and it fails
  finding expected objects.
   example: manifests/function/capm3/v0.3.1
* So trying to avoid document pull, and use current dir for workspace.
  similar to Zuul gate implementation

Change-Id: I63fd5476247f957745e15cbdfceb5fb483758e83

playbooks/vars/local-dev.yaml

@@ -20,4 +20,4 @@ proxy:
 # document pull command to download the manifests to the remote_work_dir.
 # Otherwise, the current working dir where the script is launched is used and
 # document pull is skipped.
-remote_work_dir: "/tmp/airship"
+#remote_work_dir: "/tmp/airship"

tools/gate/20_run_test_runner.sh

@@ -22,7 +22,8 @@ set -xe
 TMP_DIR=${TMP_DIR:-"$(dirname $(mktemp -u))"}
 ANSIBLE_HOSTS=${ANSIBLE_HOSTS:-"${TMP_DIR}/ansible_hosts"}
 PLAYBOOK_CONFIG=${PLAYBOOK_CONFIG:-"${TMP_DIR}/config.yaml"}
+export AIRSHIPCTL_WS=${AIRSHIPCTL_WS:-$PWD}
 
-sudo ansible-playbook -i "$ANSIBLE_HOSTS" \
+sudo --preserve-env=AIRSHIPCTL_WS ansible-playbook -i "$ANSIBLE_HOSTS" \
 	playbooks/airship-airshipctl-test-runner.yaml \
 	-e @"$PLAYBOOK_CONFIG"

tools/gate/config_template.yaml

@@ -28,4 +28,4 @@ proxy:
  http: "$HTTP_PROXY"
  https: "$HTTPS_PROXY"
  noproxy: "$NO_PROXY"
-remote_work_dir: "/tmp/airship"
+#remote_work_dir: "/tmp/airship"