Reland of Move language pak files to assets.

Reverted by:
https://codereview.chromium.org/2369683002/

Reason for reland:
I've reworked it so that:
1. The list of pak files to extract are not set on start-up, but rather lazy initialized
2. This is done by putting the list of locale assets right in base's BuildConfig.java
3. Downstream parts have been upstreams so that this won't require a 2-sided patch

Language pak files were moved to res/raw when split apks was being implemented.
Moving them to assets with a java constant keeping track of pak file locations
will improve lookup time and save some space (no more xml files and
resources.arsc).

Other notables:
- .pak filenames no longer mangled. No more .lpak. no more hyphens to _s
- Ensures that monochrome doesn't extract files by extracting only when
files are compressed.

BUG=529604

Review-Url: https://codereview.chromium.org/2371843002
Cr-Commit-Position: refs/heads/master@{#422836}


CrOS-Libchrome-Original-Commit: 67101cd0338a409d80689b9c9c875c95ccde7957
3 files changed
tree: 5a769296633b8799ddf716dbf1a2d06b4ed5311d
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/