Implements ApplyTranslateOptions in compact infobar

chrome/android/java/src/org/chromium/chrome/browser/infobar/TranslateCompactInfoBar.java

 // Copyright 2017 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 package org.chromium.chrome.browser.infobar;
 
 import android.support.design.widget.TabLayout;
 import android.view.LayoutInflater;
 import android.widget.LinearLayout;
 
@@ skipping 75 matching lines @@
             onButtonClicked(ActionType.TRANSLATE);
         }
     }
 
     @Override
     public void onTabUnselected(TabLayout.Tab tab) {}
 
     @Override
     public void onTabReselected(TabLayout.Tab tab) {}
 
-    private native void nativeApplyTranslateOptions(long nativeTranslateCompactInfoBar);
+    private native void nativeApplyTranslateOptions(
+            long nativeTranslateCompactInfoBar, int option, String value);

[gone, 2017/04/11 17:32:36]

JNI calls are expensive -- especially if you're passing strings.

1) Can you just pass five arguments all at once?
2) Why do you need a string?  You can just pass booleans and ints (which get
converted into jbooleans and jints).

[ramyasharma, 2017/04/12 00:36:40]

1. In the current code, 5 parameters are passed in the ApplyTranslateOptions.
The reason we are getting rid of that here are:
a. We don't need to pass all 5 at once in the new design, user can only change
one parameter at a time, and passing the other 4 seems like an unnecessary
overhead.
b. Having enum, and value format gives us the flexibility to add more parameters
in future without changing the API.

2. The reason for picking string, is because it covers all cases of bool, int,
string well. 

I understand there is a trade-off between passing boolean as a string vs passing
n number of parameters every time. And I prefer the single parameter way,
because it also provides a more  stable API. WDYT?

[gone, 2017/04/12 00:39:27]

I'm fine with a single parameter thing, but you should have two different apply
functions in that case: one for booleans and one for ints.  Passing Strings as a
generic parsed container is expensive.

 }