Route through a JobService when receiving a message for the GCM Driver

chrome/android/java/AndroidManifest.xml

 <?xml version="1.0" encoding="utf-8"?>
 <!-- Copyright 2015 The Chromium Authors. All rights reserved.
      Use of this source code is governed by a BSD-style license that can be
      found in the LICENSE file. -->
 
 <!--
 Note: This is a jinja2 template, processed at build time into the final manifest.
 
 Blocks denoted with { % block some_name % }foo{ % endblock % } can be overridden
 by a child template that "extends" this file.
@@ skipping 746 matching lines @@
                 <action android:name="org.chromium.chrome.browser.notifications.CLICK_NOTIFICATION" />
                 <action android:name="org.chromium.chrome.browser.notifications.CLOSE_NOTIFICATION" />
             </intent-filter>
         </receiver>
 
         <!-- Android Notification job service -->
         <service android:name="org.chromium.chrome.browser.notifications.NotificationJobService"
             android:exported="false"
             android:permission="android.permission.BIND_JOB_SERVICE"/>
 
+        <!-- Android GCM Driver job service -->
+        <service android:name="org.chromium.chrome.browser.services.gcm.GCMJobService"

[awdf, 2017/02/16 21:26:48]

Something I hadn't fully appreciated when creating the NotificationJobService is
that this is going to be set in stone forever now it's in the manifest. We could
get weird crashes if we delete or change the name of the service and someone
upgrades Chrome with a job pending for the old job service. So Android's advice
is to treat JobServices as a public api and not change them.

Hence the thought here is to create just one JobService for Chrome , it's
nonideal but more maintainable. Not sure what the advice is right now in terms
of waiting for that, Tommy?

[Peter Beverloo, 2017/02/17 15:43:59]

I'm all for that, and am definitely up for some waiting, but since I'm OOO the
week of branch point I don't want to delay this until the very last minute
either. We do need this for M58.

+            android:exported="false"
+            android:permission="android.permission.BIND_JOB_SERVICE"/>
+
         <!-- GcmTaskService implementation to wake Chrome on scheduled events -->
         <service android:name="org.chromium.chrome.browser.ChromeBackgroundService"
             android:permission="com.google.android.gms.permission.BIND_NETWORK_TASK_SERVICE"
             android:exported="true">
             <intent-filter>
                 <action android:name="com.google.android.gms.gcm.ACTION_TASK_READY" />
             </intent-filter>
         </service>
 
         <service android:name="org.chromium.chrome.browser.prerender.ChromePrerenderService"
@@ skipping 156 matching lines @@
              choose the first MediaRouteController that can play it, so the order of the list can be important.
              The most specific MediaRouteControllers should be listed first, followed by more generic ones.
              The downstream manifest replaces this block, and hence replaces the list of media route
              controllers with its own list. -->
         <meta-data android:name="org.chromium.content.browser.REMOTE_MEDIA_PLAYERS"
             android:value="org.chromium.chrome.browser.media.remote.DefaultMediaRouteController"/>
 
         {% endblock %}
     </application>
 </manifest>