Chrome on Android needs strings in java libraries to be actually used by
that java library target. We make use of android lint to hold the line
against unused resources. A follow-up CL will remove the global
suppression for components strings as well as its unused strings for
android.

This is important especially for android since each string generates
non-trivial amount of overhead due to the android system, on the order
of 3+ kilobytes for each string regardless of length.

Individual components should avoid using strings in android java files
and opt to use native strings instead, but this CL fixes the two
components that do use android-specific strings in their android code.

Bug: 731159
Change-Id: I4bfa7e0ba068bd996d710f7b6b8c8f01e0bb773d
Reviewed-on: https://chromium-review.googlesource.com/624436


Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#497053}