Minor fixes on DeploymentSupervisor

- Avoid logging 'null' criteria
  - If the `deploymentProperties` doesn't have the container matching
criteria, then the `DefaultContainerMatcher` logs saying:
"No currently available containers match criteria 'null'"

- Add `POST_INITIALIZED_EVENT` StartMode for containers path cache
start()
Also,  the logging here doesn't have any module specific info and so the logging would look like this: 

```
11:39:14,724  WARN Stream Deployer cluster.DefaultContainerMatcher - No currently available containers
11:39:17,201  WARN Stream Deployer cluster.DefaultContainerMatcher - No currently available containers
```
Maybe we can pass in ModuleDescriptor into `findAllContainersMatchingCriteria` and log that as module specific info here. What do you think?