Ensure appropriate number of data movement events are generated by a task

For every outgoing edge of a vertex, tasks need to produce data movement events for consumers. If a task does not produce a data movement event then the job will hang since the consumer task will be stuck waiting for input.
Additionally, if possible, we should check that the appropriate number of events have been produced. This may need enhancements to the edge manager API for custom edges.