Improve iOS localisation and resource packing.

Improve iOS localisation and resource packing.

Stop using whitelisting for resources from components on the rationale
that it causes confusion for the developers and most of those resources
are used on iOS.

Stop support for whitelisting for resources when using gn as meta-build
system on the rationale that the migration will happen after Chrome on
iOS is unforked at which point whitelisting will not be used with gyp
either.

Update build/ios/grit_whitelist.txt to:
1. remove all resources from //components,
2. remove all resources that no longer exists,
3. add all resources used downstream (i.e. unfork the file).

TEST=Checked that clobber build compiled and all tests passed on both
the upstream and downstream tree with this CL.

BUG=429756
Committed: https://crrev.com/502be01eec9af4fa82ce8abe4f6470735288b5e4
Cr-Commit-Position: refs/heads/master@{#350526}

[sdefresne, 2015-09-18 16:22:40]

sdefresne@chromium.org changed reviewers:
+ dpranke@chromium.org, stuartmorgan@chromium.org

[sdefresne, 2015-09-18 16:22:41]

stuartmorgan: can you review the main idea of not using whitelisting for
//components resources? 


I was not part of the decision that lead to introducing the whitelist, but I
assume it was to reduce the size of the shipped application. I think then that
it make sense not to use whitelisting for components resources as 1. most of
them are used on iOS (many of the components where developed with the goal to
share code on iOS), 2. there fewer resources in components than in chrome.

Eventually, once Chrome on iOS is unforked (and no longer using the resources
from Chrome), then we won't use whitelisting for resources from //ios. Thus I
think it make sense not to use whitelisting for //components too. If at some
points we find that the resources coming from //components are too large, I
would advocate using blacklisting instead of whitelisting (as forgetting to
update the list will not cause build failures).

WDYT?

dpranke: can you review build/secondary/tools/grit/?

[Dirk Pranke, 2015-09-18 19:31:06]

grit_rule.gni changes lgtm.

[stuartmorgan, 2015-09-22 13:17:12]

Makes sense; lgtm

If we run into specific components where unused resources are an issue, in an
unforked world the solution is grd conditionals anyway.

[sdefresne, 2015-09-22 14:44:43]

The CQ bit was checked by sdefresne@chromium.org

[sdefresne, 2015-09-22 14:44:43]

The patchset sent to the CQ was uploaded after l-g-t-m from
dpranke@chromium.org, stuartmorgan@chromium.org
Link to the patchset: https://codereview.chromium.org/1350453004/#ps20001
(title: "Update build/ios/grit_whitelist.txt")

[commit-bot: I haz the power, 2015-09-22 14:44:51]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1350453004/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1350453004/20001

[commit-bot: I haz the power, 2015-09-22 14:47:07]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-09-22 14:47:08]

Try jobs failed on following builders:
  mac_chromium_compile_dbg_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)

[sdefresne, 2015-09-22 15:10:26]

The CQ bit was checked by sdefresne@chromium.org

[sdefresne, 2015-09-22 15:10:27]

The patchset sent to the CQ was uploaded after l-g-t-m from
dpranke@chromium.org, stuartmorgan@chromium.org
Link to the patchset: https://codereview.chromium.org/1350453004/#ps40001
(title: "Rebase")

[commit-bot: I haz the power, 2015-09-22 15:10:59]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1350453004/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1350453004/40001

[commit-bot: I haz the power, 2015-09-22 15:46:06]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-09-22 15:46:07]

Try jobs failed on following builders:
  win_chromium_x64_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[sdefresne, 2015-09-23 08:16:27]

The CQ bit was checked by sdefresne@chromium.org

[commit-bot: I haz the power, 2015-09-23 08:16:51]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1350453004/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1350453004/40001

[commit-bot: I haz the power, 2015-09-23 15:47:04]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-09-23 15:47:05]

Try jobs failed on following builders:
  mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[sdefresne, 2015-09-24 08:51:35]

The CQ bit was checked by sdefresne@chromium.org

[sdefresne, 2015-09-24 08:51:35]

The patchset sent to the CQ was uploaded after l-g-t-m from
dpranke@chromium.org, stuartmorgan@chromium.org
Link to the patchset: https://codereview.chromium.org/1350453004/#ps60001
(title: "Rebase")

[commit-bot: I haz the power, 2015-09-24 08:51:40]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1350453004/60001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1350453004/60001

[commit-bot: I haz the power, 2015-09-24 10:48:21]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2015-09-24 10:49:15]

Patchset 4 (id:??) landed as
https://crrev.com/502be01eec9af4fa82ce8abe4f6470735288b5e4
Cr-Commit-Position: refs/heads/master@{#350526}