Update app runtime custom bindings to handle no WebIntents launch data.

chrome/test/data/extensions/platform_apps/launch_reply/test.js

Index: chrome/test/data/extensions/platform_apps/launch_reply/test.js
diff --git a/chrome/test/data/extensions/platform_apps/launch_reply/test.js b/chrome/test/data/extensions/platform_apps/launch_reply/test.js
deleted file mode 100644
index 7e547b9a124e787d71c28e26171d676aa73ffd2e..0000000000000000000000000000000000000000
--- a/chrome/test/data/extensions/platform_apps/launch_reply/test.js
+++ /dev/null
@@ -1,15 +0,0 @@
-// Copyright (c) 2012 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.
-
-chrome.app.runtime.onLaunched.addListener(function(launchData) {
-  // Test that there is a launchData.intent, and it is set up properly. Then
-  // immediately reply to the intent with a success message.
-  chrome.test.runTests([
-    function testIntent() {
-      chrome.test.assertFalse(!launchData, "No launchData");
-      chrome.test.assertFalse(!launchData.intent, "No launchData.intent");
-      launchData.intent.postResult(true);
-    }
-  ]);
-});