Fix success limited-repeatitions job status

Currently, limited-repeatitions job status doesn't show correctly when
it has success-ed.

For example, if the job has repeatition 1, once the job finished, then
the job status says "job has not run yet" and the success time and times
are still empty and 0, however, only "job has been disabled" shows
correctly.

Signed-off-by: Chengwei Yang <yangchengwei@qiyi.com>
Fix asynchronous job

There is another required field in mesos protocbuf message TaskStatus,
without this fix, it will throw an exception when building the protocbuf
message like below:

com.google.protobuf.UninitializedMessageException: Message missing required fields: state
        at com.google.protobuf.AbstractMessage$Builder.newUninitializedMessageException(AbstractMessage.java:605)
        at org.apache.mesos.Protos$TaskStatus$Builder.build(Protos.java:18993)
        at com.airbnb.scheduler.api.TaskManagementResource.updateStatus(TaskManagementResource.scala:48)

For the protocbuf message definination, see mesos code:
  include/mesos/mesos.proto

Signed-off-by: Chengwei Yang <yangchengwei@qiyi.com>
Fix coding style

Signed-off-by: Chengwei Yang <yangchengwei@qiyi.com>
Fix job serialization

Signed-off-by: Chengwei Yang <yangchengwei@qiyi.com>
Merge pull request #248 from chengweiv5/master

Fix limited-repeatitions job, asynchronous job and job serialization