Refactor WebApkServiceConnectionManager.

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 9aa46e7793aa5f7d3290bbf7d176c961ed4affc6..3c83cc5abccb7611b3e553dd47b80d8ceb2a890f 100644
--- a/chrome/android/webapk/shell_apk/AndroidManifest.xml
+++ b/chrome/android/webapk/shell_apk/AndroidManifest.xml
@@ -71,5 +71,14 @@
             android:process=":webapk_sandboxed_process2"
             android:exported="true"
             tools:ignore="ExportedService"/>
+        <service
+            android:name="org.chromium.webapk.shell_apk.IdentityService"
+            android:exported="true"
+            tools:ignore="ExportedService">
+            <intent-filter>
+              <action android:name="android.intent.action.MAIN" />
+              <category android:name="org.webapk.IDENTITY_SERVICE_API" />

[pkotwicz, 2017/07/14 23:20:05]

In order to be consistent with CustomTabs we should probably not have a custom
category and have a custom action. (Not sure why custom tabs made the change).
Custom tabs made the change in https://codereview.chromium.org/1234643002

I know that you are following the pattern in WebApkServiceFactory

[Xi Han, 2017/07/17 20:45:32]

This is follow the pattern to launch the WebappLauncherActivity, there are some
discussion when we changed the action there. I don't have a strong preference
though.

[pkotwicz, 2017/07/18 17:30:47]

If we make a change we will need code to handle old WebAPKs. I'd rather get this
right the first time. I understand that you are following the pattern used to
launch WebappLauncherActivity.

[Xi Han, 2017/07/18 22:36:51]

Sorry I misunderstood. I thought you want me to update the text. Sure, update
the category to action. 

+            </intent-filter>
+        </service>
     </application>
 </manifest>