FloRunner refactor

[bergman]

• make FloRunner easier to test
• return a useful Result object rather than call System.exit (replaced by FloRunner.runTask(foo).waitAndExit())
• remove the args to task and the TaskConstructor interface which was used mostly for CLI usage
• no more apollo
• no more guava
• remove json tree logging

[fabriziodemaria]

Overall looks good to me.
Regarding the new asynchronous runTask(), we could rename it runTaskAsync(). runTask() could be a blocking version that still returns the resulting value and re-throws any exception from Flo or from within the Tasks.

[bergman]

Overall looks good to me.
Regarding the new asynchronous runTask(), we could rename it runTaskAsync(). runTask() could be a blocking version that still returns the resulting value and re-throws any exception from Flo or from within the Tasks.

I opted for breaking the API. The motivation is that it is still quite early in the project and to me the async should be default.

[rouzwawi]

LGTM 👍

[danielnorberg]

Why Future (which only allows blocking get()) instead of CompletableFuture or CompletionStage ?