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.
When deploying the modules, since we no longer target **only** the arriving container but match all the available containers from the repository, can we have a `scheduled` deployer that performs the redeployment operation on a given time to all the targeting container. What I see from here is that the whole logic doesn't use the `arriving container` info anymore.