[Courses v2] Move to Meteor

See #165 for information

Closes #171
Closes #151
Closes #134 (Move to meteor build system)
Closes #133
Closes #119 (Create per schedule URL)
Closes #115
Closes #110 (Allow courses with no sections gracefully)
Closes #80 (Build this UI out)
Closes #78 (Implemented by iron router)
Closes #73 (Close - wontfix)
Closes #81 (Using heap)

Closes #165 (The tracking task for this PR)
Is there a better way to keep track of this state variable other than leaving in the global namespace?
Can `Template.scheduleSearchArea` have variables associated with it?