Add the first app_shell_browsertest test.

apps/shell/DEPS

 include_rules = [
+  # The apps module has dependencies on chrome.
+  "-apps",

[James Cook, 2014/04/08 16:03:49]

Thank you for cleaning these up.

+  # Individual subdirectories should have their own DEPS that include
+  # their allowed directories.
+  "-apps/shell",
+  "+apps/shell/common",

[James Cook, 2014/04/08 16:03:49]

If we're forcing all the DEPS into subdirectories, would it be better to force
the individual subdirs to import /common and /test?

Alternately, should we reconsider just listing all DEPS in this file?  I'm not
sure we gain that much by differentiating browser vs. renderer vs. common DEPS.

[Yoyo Zhou, 2014/04/08 21:55:21]

We could do that, but this is the pattern in chrome/ and content/ and it seems
reasonable enough.
App Shell doesn't have much going on outside of the browser process, but it's
probably still advisable to prevent stray includes of content/renderer, for
example.

+  "+apps/shell/test",
+
   # Real DEPS go in subdirectories, for example apps/shell/browser/DEPS.
   # Temporary exceptions for app_shell bring-up go here.
   # TODO(jamescook): Remove these. http://crbug.com/305404
   "!chrome/browser/extensions/extension_protocols.h",
   "!chrome/browser/extensions/extension_resource_protocols.h",
   "!chrome/common/extensions/api/generated_api.h",
   "!chrome/common/extensions/api/generated_schemas.h",
   "!chrome/common/extensions/api/sockets/sockets_manifest_handler.h",
   "!chrome/common/extensions/extension_file_util.h",
   "!chrome/common/extensions/features/base_feature_provider.h",
   "!chrome/common/extensions/features/base_feature_provider.h",
   "!chrome/common/extensions/permissions/chrome_api_permissions.h",
   "!chrome/renderer/extensions/dispatcher.h",
   "!chrome/renderer/extensions/extension_helper.h",
 ]