Introduce a new WebAPK launch action.

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 463 matching lines @@
                                running.
         -->
         <activity android:name="org.chromium.chrome.browser.webapps.WebappLauncherActivity"
             android:theme="@android:style/Theme.NoDisplay"
             android:taskAffinity=""
             android:excludeFromRecents="true">
             <intent-filter>
                 <action android:name="com.google.android.apps.chrome.webapps.WebappManager.ACTION_START_WEBAPP" />
                 <category android:name="android.intent.category.DEFAULT" />
             </intent-filter>
+            <intent-filter>
+                <action android:name="org.chromium.webapk.ACTION_START_WEBAPK" />

[Yaron, 2017/06/27 14:38:24]

wdyt about omitting "chromium" this time? Or I take it you want to keep
consistent with our package names? If so, I"m ok with it.

[Xi Han, 2017/06/27 15:05:49]

I don't have a strong preference between "org.chromium.webapk" and
"android.intent", and I am open to suggestions:)

[Yaron, 2017/06/27 15:19:41]

In the doc (#5), we selected org.webapk.ACTION_START_WEBAPK. Shall we go with
that? I could also see us renaming this to ACTION_START_WEBAPP /
ACTION_START_PWA but maybe it's ok to mention the specific implementation tech
because it affects our expectations. +Dom for general installability thoughts.
FTR I think org.webapk.ACTION_START_WEBAPK is fine, just want to give him a
chance to chime in :)

[Xi Han, 2017/06/27 17:37:17]

I am fine with "org.webapk.ACTION_START_WEBAPK" too. Let's see how Dom feels:)

+                <category android:name="android.intent.category.DEFAULT" />
+            </intent-filter>
         </activity>
         <activity-alias android:name="com.google.android.apps.chrome.webapps.WebappManager"
             android:targetActivity="org.chromium.chrome.browser.webapps.WebappLauncherActivity">
         </activity-alias>
         <activity android:name="org.chromium.chrome.browser.webapps.WebappActivity"
             android:theme="@style/WebappTheme"
             android:label="@string/webapp_activity_title"
             android:launchMode="singleTop"
             android:documentLaunchMode="intoExisting"
             android:persistableMode="persistNever"
@@ skipping 511 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>