Move remaining @CalledByNative methods out of ChromeApplication.

chrome/browser/android/preferences/preferences_launcher.h

 // 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.
 
 #ifndef CHROME_BROWSER_ANDROID_PREFERENCES_PREFERENCES_LAUNCHER_H_
 #define CHROME_BROWSER_ANDROID_PREFERENCES_PREFERENCES_LAUNCHER_H_
 
 #include <jni.h>
 #include "base/macros.h"
 
+namespace content {
+class WebContents;
+}
+
 namespace chrome {
 namespace android {
 
 class PreferencesLauncher {

[estevenson, 2017/03/22 20:06:56]

Before I submit https://codereview.chromium.org/2763133002/ I wanted to ask:

This doesn't need to be a class. Do we have a preference for classes with static
methods vs. functions in a namespace? I've seen both used fairly widely in
Chrome, the class method has the advantage that it can be used like
chrome::android::PreferencesLauncher, but it's also unnecessary, wdty?

[Ted C, 2017/03/23 03:41:15]

I have no strong preference.  I'm inclined to simply leave this as is.

  public:
   // Opens the autofill settings page.
   static void ShowAutofillSettings();
 
+  // Opens the password settings page.
+  static void ShowPasswordSettings();
+
+  // Open the clear browsing data UI.
+  static void OpenClearBrowsingData(content::WebContents* web_contents);
+
  private:
   PreferencesLauncher() {}
   ~PreferencesLauncher() {}
 
   DISALLOW_COPY_AND_ASSIGN(PreferencesLauncher);
 };
 
 }  // namespace android
 }  // namespace chrome
 
 #endif  // CHROME_BROWSER_ANDROID_PREFERENCES_PREFERENCES_LAUNCHER_H_