Use LeakCanary for all Android Service instances

Use LeakCanary for all Android Service instances

BUG=505909

[agrieve, 2016-02-13 01:09:49]

agrieve@chromium.org changed reviewers:
+ yfriedman@chromium.org

[agrieve, 2016-02-13 01:09:50]

Still a work in progress.

Before I go and do all the services (~34), let me know what you think of this
approach (but no rush. I won't be signing on again until Tuesday)

https://codereview.chromium.org/1697603002

[agrieve, 2016-02-13 01:11:45]

On 2016/02/13 01:09:50, agrieve wrote:
> Still a work in progress.
> 
> Before I go and do all the services (~34), let me know what you think of this
> approach (but no rush. I won't be signing on again until Tuesday)
> 
> https://codereview.chromium.org/1697603002

Note (half for myself) - that this *does* increase the classes.dex size. I did a
dexdump + diff and it's from:
1. The new Util class is not stripped (likely because we explicitly tell
proguard to -keep all of our classes)
2. There are some new onDestroy overrides, that even though they are no-ops
(just call super), are not stripped. 

I plan to see if I can address both of these with a new proguard eventually, but
for now, we're talking ~400 bytes.

[Yaron, 2016-02-16 20:24:17]

approach seems good to me. agree that 400 bytes isn't a big issue. I naively
hoped that proguard would remove functions that just call super