We recently began altering the mount map used by the wrapper driver
for each execution run (so that we can only include the current
playbook). However, the setMountsMap method operates on the global
driver object rather than an object more closely bound to the lifetime
of the playbook run. The fact that this works at all is just luck
(executing process is slow enough that hitting a race condition where
the wrong directories are mounted is unlikely).
To correct this, add a new layer which contains the context for the
current playbook execution.
Change-Id: I3a06f19e88435a49c7b9aea4e1221b812f5a43d0
ce56ff9756