Android web notifications: Schedule job instead of starting service (N+)

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 02ecd0d2d99efb7c9ffa9657d0dee2ddf465e47d..10ef9a2f4870d69f88ca179ff30b60db0c72495f 100644
--- a/chrome/android/java/AndroidManifest.xml
+++ b/chrome/android/java/AndroidManifest.xml
@@ -786,7 +786,8 @@ by a child template that "extends" this file.
 
         <!-- Android Notification service listener -->
         <service android:name="org.chromium.chrome.browser.notifications.NotificationService"
-            android:exported="false"/>
+            android:exported="false"
+            android:permission="android.permission.BIND_JOB_SERVICE"/>

[Peter Beverloo, 2017/01/09 14:28:05]

This is API level 21, will it be ignored by earlier versions? I'd like an OWNER
of this file to confirm it won't complicate our update path.

[awdf, 2017/01/11 14:56:17]

I think this would just be ignored. Still installs fine on K - I checked. 

However it *is* a problem to use the same service on all platforms, because
JobService, which the JobScheduler requires us to inherit from, is API 21+, so
we need a different service for at least pre-L. (Also I forgot to actually leave
in the code to handle the normal start service call when I adapted it for
startJob :D )

I'll fix this and check it works on all platforms.

         <receiver android:name="org.chromium.chrome.browser.notifications.NotificationService$Receiver"
             android:exported="false">
             <intent-filter>