Make ChoiceSetManager operations blocking

[bilal-alsharifi]

Fixes #1157

This PR is ready for review.

Risk

This PR makes no API changes.

Testing Plan

Test using ChoiceSetManager and make sure that all operations are handled correctly

Summary

This PR changes how the executor service handles operations in ChoiceSetManager to make the operations block until all async calls are completely finished. With this fix, the executor doesn't start executing the next operation until the current operation calls finishOperation()

CLA

• I have signed the CLA

[NicoleYarroch]

The test cases are not compiling for me.

[codecov-io]

Codecov Report

Merging #1155 into feature/cancel_interaction_RPC will increase coverage by 3.16%.
The diff coverage is 48.23%.

@@                         Coverage Diff                          @@
##             feature/cancel_interaction_RPC    #1155      +/-   ##
====================================================================
+ Coverage                             43.99%   47.16%   +3.16%     
+ Complexity                             4259     4128     -131     
====================================================================
  Files                                   462      462              
  Lines                                 25416    22674    -2742     
  Branches                               3286     2577     -709     
====================================================================
- Hits                                  11183    10694     -489     
+ Misses                                13511    11324    -2187     
+ Partials                                722      656      -66

Impacted Files	Coverage Δ	Complexity Δ
...rs/screen/choiceset/PresentChoiceSetOperation.java	40.33% <16.66%> (-2.36%)	18 <0> (ø)
...gers/screen/choiceset/PreloadChoicesOperation.java	20% <20%> (-0.73%)	12 <1> (ø)
...agers/screen/choiceset/DeleteChoicesOperation.java	28.57% <20%> (-3.69%)	3 <1> (ø)
...anagers/screen/choiceset/BaseChoiceSetManager.java	39.31% <22.22%> (+1.26%)	24 <2> (-1)	⬇️
...ers/screen/choiceset/PresentKeyboardOperation.java	38.92% <37.5%> (-10.73%)	13 <1> (-1)
...reen/choiceset/CheckChoiceVROptionalOperation.java	27.27% <42.85%> (+0.6%)	6 <2> (ø)	⬇️
...nagers/screen/choiceset/AsynchronousOperation.java	93.33% <90%> (-1.67%)	14 <11> (+6)
...tdevicelink/managers/video/VideoStreamManager.java	38.73% <0%> (-6.21%)	13% <0%> (-1%)
...smartdevicelink/encoder/VirtualDisplayEncoder.java	24.43% <0%> (-4.55%)	8% <0%> (ø)
... and 14 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b7039e3...3b610a8. Read the comment docs.

[bilal-alsharifi]

@NicoleYarroch I updated the tests to make them compile. But then I had to comment out the cancel interactions tests temporarily. Because I noticed that in these tests, operation.run() is called to start the operation which makes the runnable run on the main thread. In real life, operations should run in a different thread (the executor service thread). I added a more detailed comment about that in the cancel interaction PR.
Because the operations run on the same thread in the tests, calling block() in the operation.run() function will block that main thread which causes the tests to get stuck and Travis to timeout.

I will keep these tests temporarily commented out until we decide how to handle operation canceling in the original cancel interaction PR.