GitLab

This removes the native side of AwSafeBrowsingConfigHelper and the
related AwContentsStatics methods. The native AwSafeBrowsingConfigHelper
previously only maintained a global variable to keep track of manifest
opt-in. However, we currently only set/get that value from the Java
side. Therefore, we can remove the native side and keep track of this
value in a static Java variable.

This appears to be the culprit for some startup delay, so this is
expected to improve startup time as well.

R=torne@chromium.org

      conditions (including manifest opt-in/out)
      (seems to be a noticeable startup win, net reduction of 23 ms locally)

Bug: 859696
Test: manual - use SuperSafeBrowsing test app, check a variety of opt-in
Test: tools/perf/run_benchmark system_health.webview_startup --browser android-webview-google
Change-Id: I520c405027991101b5c8c23c58853c6b7c73c2b3
Reviewed-on: https://chromium-review.googlesource.com/1123887
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#572366}