Makes WebAPK handle NOTIFICATION_PREFERENCES intents

chrome/android/webapk/shell_apk/AndroidManifest.xml

Index: chrome/android/webapk/shell_apk/AndroidManifest.xml
diff --git a/chrome/android/webapk/shell_apk/AndroidManifest.xml b/chrome/android/webapk/shell_apk/AndroidManifest.xml
index 14e2062a22b78c210471d1e2f8aefc7b187fed90..893f031f06830e03926b715a11a10149a568d4eb 100644
--- a/chrome/android/webapk/shell_apk/AndroidManifest.xml
+++ b/chrome/android/webapk/shell_apk/AndroidManifest.xml
@@ -30,7 +30,15 @@
                 <data android:scheme="https" android:host="{{ scope_url_host }}" android:pathPrefix="/"></data>
             </intent-filter>
         </activity>
+        <activity android:name="org.chromium.webapk.shell_apk.NotificationSettingsLauncherActivity">
+            <intent-filter>
+                <action android:name="android.intent.action.MAIN"/>
+                <category android:name="android.intent.category.NOTIFICATION_PREFERENCES"/>
+            </intent-filter>
+        </activity>
         <meta-data android:name="runtimeHost" android:value="{{ runtime_host }}" />
+        <meta-data android:name="hostNotificationPreferencesHandler"

[Yaron, 2016/07/25 14:28:27]

I'm thinking that it would be nice to limit the number of new manifest fields we
introduce. If we do need to add them, then we should try and add them with some
generality to try and limit the number of variables. This would make it easier
to push new versions and not depend on new server releases (to populate those
variables).

Since this will be rare, it's ok to me if it's not the most optimal. Can we
instead add logic to the runtime_library to scan the host browser's manifest for
a NOTIFICATION_PREFERENCES handler and intent to that? Or is that even necessary
- could you just send this intent (act=android.intent.action.MAIN,
cat=android.intent.category.NOTIFICATION_PREFERENCES) at the host browser
package?

Alternatively, we could add a "MainActivity" class. Then a requirement for
webapk host is that your main activity must be able to handle this intent.

[pkotwicz, 2016/07/25 18:23:25]

I changed the intent to be sent solely to the browser package. It seems to work

+                   android:value="{{ host_notification_preferences_handler }}" />
         <meta-data android:name="startUrl" android:value="{{ start_url }}" />
         <meta-data android:name="name" android:value="{{ name }}" />
         <meta-data android:name="scope" android:value="{{ scope_url }}" />