Bundle some ash resources into chrome for mash=1 use_ash=0

Bundle some ash resources into chrome for mash=1 use_ash=0

Today it is possible to build the 'chrome' target with
mash enabled on both ChromeOS and Linux desktop builds,
by setting 'enable_package_mash_services=true' in the GN arguments.

In case of ChromeOS builds, 'use_ash' is enabled by default,
and the ash resources (localized strings, icons, etc), are 
bundled into the 'chrome' executable just normally.

In case of non-chromeos mash builds though, although 'use_ash'
is false by default, some code in //src/ash/ is still used because
//chrome/app/mash does depend on ash.

This CL temporarily allows some ash_resources to be bundled into 'chrome',
when 'enable_package_mash_services' is true.

In practice, without the ash_resources bundled into chrome, chrome
launches like https://goo.gl/9mbQA5 (see the missing resources).
On the other hand, with the ash_resource bundled, chrome launches like
https://goo.gl/0R9Sl3 .

BUG=

[tonikitoo, 2016-11-07 17:50:46]

Description was changed from

==========
Use some ash resources for mash=1 use_ash=0

BUG=295089
==========

to

==========
Use some ash resources for mash=1 use_ash=0

BUG=295089
==========

[tonikitoo, 2016-11-09 20:04:23]

Description was changed from

==========
Use some ash resources for mash=1 use_ash=0

BUG=295089
==========

to

==========
Bundle some ash resources into chrome for mash=1 use_ash=0

Today it is possible to build the 'chrome' target with
mash enabled on both ChromeOS and Linux desktop builds,
by setting 'enable_package_mash_services=true' in the GN arguments.

In case of ChromeOS builds, 'use_ash' is enabled by default,
and the ash resources (localized strings, icons, etc), are 
bundled into the 'chrome' executable just normally.

In case of non-chromeos mash builds though, although 'use_ash'
is false by default, some code in //src/ash/ is still used because
//chrome/app/mash does depend on ash.

This CL temporarily allows some ash_resources to be bundled into 'chrome',
when 'enable_package_mash_services' is true.

In practice, without the ash_resources bundled into chrome, chrome
launches like https://goo.gl/9mbQA5 (see the missing resources).
On the other hand, with the ash_resource bundled, chrome launches like
https://goo.gl/0R9Sl3 .

BUG=
==========

[tonikitoo, 2016-11-09 20:04:23]

tonikitoo@igalia.com changed reviewers:
+ sky@chromium.org, thomasanderson@chromium.org

[tonikitoo, 2016-11-09 20:26:30]

Spin off of https://codereview.chromium.org/2408803002/

@sky: I tried to explain in the commit message the reason, as well as stated
that this solution is temporary, so let others (including ozone/linux bots) to
run with it.

[sky, 2016-11-09 22:27:33]

Again, I think this is the wrong way to go about this. You shouldn't be
compiling ash files in a non-ash build.