XD-1984: all modules deploy to the first container

When a container arrives, use the `RedeploymentContainerMatcher` to issue deployments for unallocated modules. This reuses the logic for container departure.

This change makes it less likely that a system restart will result in all modules being deployed to the first container that arrives in the cluster.

A side effect of this change is that `ArrivingContainerModuleRedeployer` no longer needs to query for the deployments on an arriving container because the redeploy logic for modules in `ModuleRedeployer` already prevents the deployment of duplicate modules to a container.
IMHO, this logic in `ArrivingContainerModuleRedployer` needs to be moved out of the `ContainerListener`. Here are the reasons I think of:
1) Since the same logic gets called everytime the container arrives, we may be same thing over and over though the potential matching containers are the same.
2) When the admin leadership changes, the `onChildAdded` event is going to get called for all the existing containers in the cluster though we know we already matched all the containers. Hence this could be a over kill.