Communicate task completion to Scheduler interface. Add two schedulers

[sacheendra]

Summary

Currently, the scheduling cycle for each task scans all available hosts. This is necessary because the scheduler doesn't know each host's capacity.
The scheduler can track each host's capacity if it knowns when each task starts and ends. I added an additional function to the scheduler interface to track task ends. The scheduler now also receives multiple tasks to schedule at a time, rather than just one.

Using the interface, I implement two new schedulers: 1) A memorizing one, which uses a calender priority queue to track which host is least occupied. 2) A power of two random choices scheduler.

Implementation Notes ⚒️

• The scheduler now accept multiple tasks with a select(iter: MutableIterator<Task>): HostView? interface instead of select(task: Task): HostView?. This allows the scheduler to pick a task which is not at the top of the queue.
• The Task interface now has a field, timeSkipped, which keeps track of how many time the task was skipped when it was at the head of the queue. If a task has been skipped a specified maximum number of times, no other task is scheduled until this one is.

External Dependencies 🍀

Breaking API Changes ⚠️

Simply specify none (N/A) if not applicable.