Add origin of settings reset request to feedback reports.

chrome/browser/profile_resetter/profile_reset_report.proto

Index: chrome/browser/profile_resetter/profile_reset_report.proto
diff --git a/chrome/browser/profile_resetter/profile_reset_report.proto b/chrome/browser/profile_resetter/profile_reset_report.proto
index 4187c7aee0974f4f8f698088eaf6a214d3752945..be6141a1e652c2698f3fe8fe630d1dd11bae4252 100644
--- a/chrome/browser/profile_resetter/profile_reset_report.proto
+++ b/chrome/browser/profile_resetter/profile_reset_report.proto
@@ -62,5 +62,22 @@ message ChromeResetReport {
   // Full command line (executable and parameters) of shotcuts to start Chrome.
   repeated string shortcuts = 18;
 
-  // next available tag number: 19.
+  // Specifies where the request for the settings reset came from.
+  enum ResetRequestOrigin {
+    RESET_REQUEST_ORIGIN_UNSPECIFIED = 0;
+    // User clicked on the reset button on the settings page.
+    RESET_REQUEST_ORIGIN_USER_CLICK = 1;
+    // A settings reset was requested by the Chrome Cleanup Tool.
+    RESET_REQUEST_ORIGIN_CCT = 2;
+    // The triggered settings reset API was used.
+    RESET_REQUEST_ORIGIN_TRIGGERED_RESET = 3;
+    // None of the other cases. Possibly by navigating to
+    // chrome://settings/resetProfileSettings directly or launching
+    // chrome with that URL as an argument.
+    RESET_REQUEST_ORIGIN_UNKNOWN = 4;
+  }
+
+  optional ResetRequestOrigin reset_request_origin = 19;
+
+  // next available tag number: 20.
 }