Add SourceUI field to permission report

chrome/browser/permissions/permission_context_base.cc

Index: chrome/browser/permissions/permission_context_base.cc
diff --git a/chrome/browser/permissions/permission_context_base.cc b/chrome/browser/permissions/permission_context_base.cc
index 9487ad0efc570d93c012fa1aabc3e0562174e63b..a4fc3bb968d5c28d812039d0be1b74a2ce1410f8 100644
--- a/chrome/browser/permissions/permission_context_base.cc
+++ b/chrome/browser/permissions/permission_context_base.cc
@@ -217,14 +217,14 @@ void PermissionContextBase::PermissionDecided(
            content_setting == CONTENT_SETTING_BLOCK);
     if (content_setting == CONTENT_SETTING_ALLOW)
       PermissionUmaUtil::PermissionGranted(permission_type_, requesting_origin,
-                                           profile_);
+                                           PROMPT, profile_);

[raymes, 2016/07/12 00:54:36]

As discussed, I think in most cases we don't need to pass the SourceUI here
because we can infer it from the operation (e.g. PermissionGranted can only be
called for prompts).

[kcarattini, 2016/07/12 01:01:42]

I assume that we don't call it for anything but the prompt now, but will that
change? E.g. OIB or Site Settings?

[stefanocs, 2016/07/12 04:33:33]

Done.

     else
       PermissionUmaUtil::PermissionDenied(permission_type_, requesting_origin,
-                                          profile_);
+                                          PROMPT, profile_);
   } else {
     DCHECK_EQ(content_setting, CONTENT_SETTING_DEFAULT);
     PermissionUmaUtil::PermissionDismissed(permission_type_, requesting_origin,
-                                           profile_);
+                                           PROMPT, profile_);
   }
 #endif