Add distributed primitives

[jpsamaroo]

Once #117 is merged, and #166 is realized, we'll want users to be able to use Dagger for traditional concurrent programming. In order to do so, we need to be able to ensure certain scheduling patterns and communication between thunks. Important primitives include:

• Barrier
• Co-scheduling (two or more thunks are guaranteed to be scheduled concurrently)
• Co-execution (same as co-scheduling, and the thunks will execute on the same type of processor (for shared-memory operations))
• Wait on thunk completion (one or more)
• Get thunk result
• Block/cancel thunk scheduling

The above primitives would enable #140 (comment)

[jpsamaroo]

Waiting on thunk completion and fetching thunk results will be implemented in #117