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.
That's right, we don't examine the arriving container anymore since it is assumed that the arriving container will be considered for deployment by the existing container matcher logic. Do you think it needs to be done async?