MULE-6831: Applications deleted when deployment fails

_ Cleaning test code
(cherry picked from commit 3800199)
(cherry picked from commit 840c902)
MULE-6831: Applications deleted when deployment fails

_ Cleaning test code
(cherry picked from commit ef22b77)
(cherry picked from commit 0e99602)
MULE-6831: Applications deleted when deployment fails

_ Adding a system property to configure the interval used to check for updated apps in the MuleDeploymentService
(cherry picked from commit c9d26e3)
(cherry picked from commit e3db921)
MULE-6831: Applications deleted when deployment fails

_  Cleaning tests
(cherry picked from commit d4134cb)
(cherry picked from commit 9d4c822)
MULE-6831: Applications deleted when deployment fails

_  Fixing flaky test
(cherry picked from commit 4070c95)
(cherry picked from commit 3834c97)
MULE-6831: Applications deleted when deployment fails

_  Fixing flaky test: all test should add applications using the synchronized utility methods
(cherry picked from commit 12cd91f)
(cherry picked from commit 10ec073)
MULE-6831: Applications deleted when deployment fails

_  Fixing flaky tests: AppDirWatcher#run can be executed twice before mockito verifies the interaction with the mock. This flaky test was a really caused by a bug. Fixed decoding zombie file' urls
(cherry picked from commit 5fcc340)
(cherry picked from commit b4932a6)
MULE-6831: Applications deleted when deployment fails

_ Fixing flaky test: org.mule.module.launcher.DeploymentServiceTestCase#deploysInvalidExplodedAppAfterStartup by synchronizing access to applications in MuleDeploymentService#stop
(cherry picked from commit cc61a02)
(cherry picked from commit 0c7933f)