Remove --disable-app-shims.

apps/app_shim/app_shim_mac.cc

Index: apps/app_shim/app_shim_mac.cc
diff --git a/apps/app_shim/app_shim_mac.cc b/apps/app_shim/app_shim_mac.cc
index a809fa74e58e1532a070c461e2135ce31b6fd80f..a93c2a837b4b3b801c9bd5fd27b89e6a255f5d96 100644
--- a/apps/app_shim/app_shim_mac.cc
+++ b/apps/app_shim/app_shim_mac.cc
@@ -12,8 +12,7 @@ namespace apps {
 bool IsAppShimsEnabled() {
   // Disable app shims in tests because shims created in ~/Applications will not
   // be cleaned up.

[tapted, 2014/05/22 04:11:11]

Is this the only reason? That is, can we move this function to an anonymous
namespace in web_app_mac.mm and achieve the same?

[jackhou1, 2014/05/22 04:59:58]

Hmm, when I was considering this, I thought it was better as-is because the
check happens earlier on the UI thread. The entry points in web_app_mac are all
on the FILE thread. On looking at it again, that seems a minor issue. Moving it
to web_app_mac would also simplify AppShortcutsManager::OnceOffCreateShortcuts.

-  return !(CommandLine::ForCurrentProcess()->HasSwitch(switches::kTestType) ||
-      CommandLine::ForCurrentProcess()->HasSwitch(switches::kDisableAppShims));
+  return !CommandLine::ForCurrentProcess()->HasSwitch(switches::kTestType);
 }
 
 }  // namespace apps