arc: Handle ARC events in MD Settings

chrome/browser/resources/settings/android_apps_page/android_apps_browser_proxy.js

Index: chrome/browser/resources/settings/android_apps_page/android_apps_browser_proxy.js
diff --git a/chrome/browser/resources/settings/android_apps_page/android_apps_browser_proxy.js b/chrome/browser/resources/settings/android_apps_page/android_apps_browser_proxy.js
index 1a2e0be7b987c842dda14a0c04cbd6e71264d511..89b59072cedba073b73dbbd6979f9d29b8b48163 100644
--- a/chrome/browser/resources/settings/android_apps_page/android_apps_browser_proxy.js
+++ b/chrome/browser/resources/settings/android_apps_page/android_apps_browser_proxy.js
@@ -8,7 +8,11 @@
  */
 
 /**
- * @typedef {{appReady: boolean}}
+/**
+ * @typedef {{
+ *   playStoreEnabled: boolean,
+ *   appSettingsAvailable: boolean,

[stevenjb, 2017/05/10 16:47:03]

nit: document each of these. I know we use 'Play Store' for the user facing
messaging, but I still think of the feature availability as 'ARC'.
also: maybe 'settingsAppAvailable'?

[khmel, 2017/05/10 21:48:12]

Some times ago we changed meaning ARC available to Play Store available. There 
is current work to use ARC without the Play Store and we distinguish Play Store
and ARC availability.  Also renamed.

+ * }}
  * @see chrome/browser/ui/webui/settings/chromeos/android_apps_handler.cc
  */
 var AndroidAppsInfo;