Separate Logistical Code from UI Code in SchedulingActivity

ideally the logistical code is separated from the ui code thru a method call, where the logic code can live in the presenter and the ui code lives in the activity. combining both makes the file more difficult to read -- this is just one ex of the need for a presenter in this file

_Originally posted by @ningning621 in https://github.com/cuappdev/pear-android/pull/3_

首先阅读 SchedulingActivity，并确定哪些代码负责调度逻辑，哪些代码负责 UI 职责。定义 issue 中描述的 presenter 边界，将后勤处理移到方法调用之后，并验证 activity 仍负责 UI 行为，同时不改变调度功能。

由索引模型根据 Issue 内容生成。