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

chrome/android/java/AndroidManifest.xml

Index: chrome/android/java/AndroidManifest.xml
diff --git a/chrome/android/java/AndroidManifest.xml b/chrome/android/java/AndroidManifest.xml
index b5b9a97aa9c4db1357f2f7c05663ec170e94cbf3..95581dd7186d38e52f90dd75b7445bbc63f166a4 100644
--- a/chrome/android/java/AndroidManifest.xml
+++ b/chrome/android/java/AndroidManifest.xml
@@ -764,6 +764,11 @@ by a child template that "extends" this file.
             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"