Would you prefer to split out menu stop vs toolbar stop (i.e. phone vs tablet)?

We actually have two reload actions defined, MobileToolbarReload and MobileMenuReload, but we never actually used MobileMenuReload.

If we want to split menu vs toolbar, then we'll do it for both reload and a newly added stop.  Otherwise, we'll just add another one for Stop

I'm fine merging them as MobileToolbarStop. All other tablet + phone actions are merged so it might be confusing to introduce a split and we can always manually split the actions out by tablet/phone if we want to.

Looked a bit more at this and it seems like most places do track toolbar vs menu separately, so I actually think we should do this here too.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2f58462eb176193fd017c8a5e724436cb43d37b5

commit 2f58462eb176193fd017c8a5e724436cb43d37b5
Author: tedchoc <tedchoc@chromium.org>
Date: Mon Sep 19 21:50:21 2016

Add a user action for stop in Android.

This also splits out reload tracking to be from menu (phones)
vs from toolbar (tablets), which is consistent with the other
actions such as download.

BUG= 645294 

Review-Url: https://codereview.chromium.org/2341593003
Cr-Commit-Position: refs/heads/master@{#419577}

[modify] https://crrev.com/2f58462eb176193fd017c8a5e724436cb43d37b5/chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java
[modify] https://crrev.com/2f58462eb176193fd017c8a5e724436cb43d37b5/chrome/android/java/src/org/chromium/chrome/browser/toolbar/ToolbarManager.java
[modify] https://crrev.com/2f58462eb176193fd017c8a5e724436cb43d37b5/tools/metrics/actions/actions.xml