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()
Yeah, I thought about it. But the Stream/JobDeploymentListener has this logging:

```
logger.warn("No containers available for deployment of stream {}", stream.getName());
```

Do you think we can still have the logging at DefaultContainerMatcher as it is `module` level?