Tie Container placement service and Container placement handler and validate placement requests

On job restarts, there might be already pending container placement requests from the previous deployment. Since a new deploy can potentially change the job state (some containers might lose affinity), we should not allow pending control actions to be taken from the previous deployment

Also even if the metastore is eventually consistent, duplicate actions delivered to the metastore should be only taken once, allow queuing / dequeuing logic for container placement requests