Support multi-process task scheduling

[Vandalko]

Current Goro implementation heavily relies on the fact that GoroService is in the same process.

The check here:
https://github.com/stanfy/goro/blob/v3.0.0-RC3/goro/src/main/java/com/stanfy/enroscar/goro/Goro.java#L26

which is invoked here:
https://github.com/stanfy/goro/blob/v3.0.0-RC3/goro/src/main/java/com/stanfy/enroscar/goro/BoundGoro.java#L61

is required to obtain Goro instance from GoroService, which, in fact, was plugged in using GoroService.setup method.

But BoundGoro should send tasks to the GoroService, instead.

P.S. Currently, the only purpose of GoroService is to keep application alive, because it does not provide any IPC functions - it operates on the same Goro which was provided during setup.

[roman-mazur]

Well, it was never told GoroService is supposed to work in a multi process environment...
Main Goro interfaces is goro.schedule(Callable). If we we introduce multiprocess features, this interface will have to be restricted to accept Parcelables only. This will cause usage issues.

[Vandalko]

But there is 2 different interfaces: Goro and BoundGoro.
Also, GoroService.taskIntent requires Parcelable task.
So, at the end, it is not really clear that:

GoroService is not supposed to work in a multi process environment...

I understand that having BoundGoro and GoroService.taskIntent simply implies that goro interacts with local service, but that makes a very little gain...