Move each permission classes to its own files in extensions/permissions

chrome/browser/extensions/extension_info_map.h

Index: chrome/browser/extensions/extension_info_map.h
diff --git a/chrome/browser/extensions/extension_info_map.h b/chrome/browser/extensions/extension_info_map.h
index 8a64d55fdfba63f4bb56b6bcf66e03c163d55a33..292b80471df8c039078e956ae18d20cdff8fbd3e 100644
--- a/chrome/browser/extensions/extension_info_map.h
+++ b/chrome/browser/extensions/extension_info_map.h
@@ -17,6 +17,8 @@
 #include "chrome/common/extensions/extension_constants.h"
 #include "chrome/common/extensions/extension_set.h"
 
+using extensions::APIPermission;

[miket_OOO, 2012/06/25 22:01:11]

In a case like this file where there's only a single usage of this constant, I
think it'd be more natural just to put the extensions namespace in front of the
usage, rather than having a "using" at the top. Since this is a great big CL,
I'm not going to insist on it, but as-is this file looks weird, and I urge you
to consider cleaning it up.

[Peng, 2012/06/25 22:49:01]

Done.

+
 namespace extensions {
 class Extension;
 }
@@ -70,7 +72,7 @@ class ExtensionInfoMap : public base::RefCountedThreadSafe<ExtensionInfoMap> {
   // |origin| in |process_id| with |permission|.
   bool SecurityOriginHasAPIPermission(
       const GURL& origin, int process_id,
-      ExtensionAPIPermission::ID permission) const;
+      APIPermission::ID permission) const;
 
   ExtensionsQuotaService* GetQuotaService();