Rearrange deps in JavaLibrary.mk

For build targets with lots of dependencies (which are
likely to gain or lose dependencies in future), break
the dependencies out over separate lines and order them
alphabetically. This has the benefit that it

 a) minimizes the risk of merge conflicts in future
 b) allows blame/annotate to identify the originating
    CL for dependencies added from now on.

Test: make droid cts
Change-Id: I2df930461b3a6611dcfde2c54d100daf0c4222da