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