Move new tab UMA logging to the click handler

Previously the logging was done in ToolbarPhone. This meant that
Duet wasn't logging any of the new tab button clicks. This moves
the logging to the click handler.

Bug: 910682
Change-Id: I318ccdeffdb453e97cca8e3a203177b5db2f1791
Reviewed-on: https://chromium-review.googlesource.com/c/1357381
Commit-Queue: Pedro Amaral <amaralp@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612855}

chrome/android/java/src/org/chromium/chrome/browser/ChromeTabbedActivity.java

@@ -845,6 +845,8 @@ public class ChromeTabbedActivity
                 // newtab button on the toolbar.
                 getCurrentTabCreator().launchNTP();
                 mLocaleManager.showSearchEnginePromoIfNeeded(ChromeTabbedActivity.this, null);
+                RecordUserAction.record("MobileToolbarStackViewNewTab");
+                RecordUserAction.record("MobileNewTabOpened");
             };
             OnClickListener bookmarkClickHandler = v -> addOrEditBookmark(getActivityTab());
 

chrome/android/java/src/org/chromium/chrome/browser/toolbar/top/ToolbarPhone.java

@@ -52,7 +52,6 @@ import android.widget.TextView;
 import org.chromium.base.ApiCompatibilityUtils;
 import org.chromium.base.TraceEvent;
 import org.chromium.base.VisibleForTesting;
-import org.chromium.base.metrics.RecordUserAction;
 import org.chromium.chrome.R;
 import org.chromium.chrome.browser.ChromeFeatureList;
 import org.chromium.chrome.browser.compositor.Invalidator;
@@ -582,9 +581,6 @@ public class ToolbarPhone
 
             if (mNewTabListener != null) {
                 mNewTabListener.onClick(v);
-                RecordUserAction.record("MobileToolbarStackViewNewTab");
-                RecordUserAction.record("MobileNewTabOpened");
-                // TODO(kkimlabs): Record UMA action for homepage button.
             }
         } else if (mHomeButton != null && mHomeButton == v) {
             openHomepage();