Revert of Relanding [Android] Adding Smart GO/NEXT feature in Chrome

Revert of Relanding [Android] Adding Smart GO/NEXT feature in Chrome (patchset #4 id:80001 of https://codereview.chromium.org/2948593002/ )

Reason for revert:
This caused perf regression on browse_social_facebook_infinite_scroll
test on most platforms.

See crbug.com/737388 for details.

Original issue's description:
> Relanding [Android] Adding Smart GO/NEXT feature in Chrome
> 
> Smart Go/Next brings better user experience to the user during form submitting applications.
> For navigating between form elements, user can use NEXT/PREVIOUS button from IME
> without touching on individual fields. This will avoid unnecessary form submissions before
> filling or visiting all fields in the form.
> 
> Additionally it will save user time and avoid redundant network requests before actually
> filling/attending entire fields in the form
> 
> Design Document: https://docs.google.com/document/d/1h0diigZ8LUi7A3UKJ_zwNUbvNQoe-Nwr55_p6ivSPNg/edit?usp=sharing
> 
> Initial patch is reviewed @ https://codereview.chromium.org/2839993002/
> 
> BUG=410785, 648986, 733222
> 
> Review-Url: https://codereview.chromium.org/2948593002
> Cr-Commit-Position: refs/heads/master@{#481868}
> Committed: https://chromium.googlesource.com/chromium/src/+/4eb6812cc312e4ea919518a4e3087944e31b3b72

TBR=yosin@chromium.org,aelias@chromium.org,changwan@chromium.org,dcheng@chromium.org,kochi@chromium.org,tedchoc@chromium.org,tkent@chromium.org,yfriedman@chromium.org,nasko@chromium.org,ajith.v@samsung.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=410785, 648986, 733222

[Takayoshi Kochi (Google), 2017-06-28 05:43:54]

The CQ bit was checked by kochi@google.com

[Takayoshi Kochi (Google), 2017-06-28 05:43:54]

Created Revert of Relanding [Android] Adding Smart GO/NEXT feature in Chrome

[commit-bot: I haz the power, 2017-06-28 05:44:05]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-06-28 05:44:06]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-06-28 05:44:07]

No L-G-T-M from a valid reviewer yet.
CQ run can only be started once the patch has received an L-G-T-M from a full
committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,_not_ a
full super star committer.
Committers are members of the group "project-chromium-committers".
Note that this has nothing to do with OWNERS files.

[tkent, 2017-06-28 05:44:33]

lgtm

[Takayoshi Kochi (Google), 2017-06-28 05:45:45]

The CQ bit was checked by kochi@google.com

[commit-bot: I haz the power, 2017-06-28 05:45:57]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[tkent, 2017-06-28 05:46:00]

The CQ bit was checked by tkent@chromium.org

[commit-bot: I haz the power, 2017-06-28 05:46:13]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-06-28 05:48:34]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-06-28 05:48:35]

Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)

[Takayoshi Kochi (Google), 2017-06-28 06:21:01]

The conflict is in WebLocalFrame.h (one line diff in
include headers).

For some unknown reason I cannot update this CL, I uploaded
the fixed CL at
https://chromium-review.googlesource.com/c/551697/