Move networking_private to src/extensions

extensions/common/permissions/extensions_api_permissions.cc

Index: extensions/common/permissions/extensions_api_permissions.cc
diff --git a/extensions/common/permissions/extensions_api_permissions.cc b/extensions/common/permissions/extensions_api_permissions.cc
index 617ed503a6b2dcca9f5b3d0fd4b7e2e62fbdf04e..2af48cbf30b3f71be3e4bfb499b1d9c9991edb88 100644
--- a/extensions/common/permissions/extensions_api_permissions.cc
+++ b/extensions/common/permissions/extensions_api_permissions.cc
@@ -69,6 +69,11 @@ std::vector<APIPermissionInfo*> ExtensionsAPIPermissions::GetAllPermissions()
       {APIPermission::kOverrideEscFullscreen,
        "app.window.fullscreen.overrideEsc"},
       {APIPermission::kIdle, "idle"},
+      {APIPermission::kNetworkingPrivate,
+       "networkingPrivate",
+       APIPermissionInfo::kFlagCannotBeOptional,

[asargent_no_longer_on_chrome, 2015/01/27 18:31:00]

Is there any reason why this permission cannot be optional? In general we'd
prefer that all permissions be available optionally whenever possible. (I
realize this is the way it was before; just wondering if there was a good reason
or it was just cargo culting other code)

[stevenjb, 2015/01/27 19:24:51]

I think this is OK for now. This is a private API and it is highly unlikely that
something using this API wouldn't be badly broken without it.

That said, we can certainly discuss this separately and consider changing to
granting permissions on demand in the future. For the public networking APIs we
are working on that definitely seems like a better approach.

+       IDS_EXTENSION_PROMPT_WARNING_NETWORKING_PRIVATE,
+       PermissionMessage::kNetworkingPrivate},
       {APIPermission::kPower, "power"},
       {APIPermission::kPrinterProvider, "printerProvider"},
       {APIPermission::kSerial,