AW: remove redundant proguard rule

This removes a redundant proguard rule to keep AwSafeBrowsingApiHandler.
This rule used to be meaningful when AwSafeBrowsingApiHandler was loaded
by reflection, but this is no longer true (it's still instantiated via
reflection, but that's handled elsewhere by annotating the constructor
with @UsedByReflection).

This is mostly a simplification, but this may be a small binary size
win, by permitting proguard/R8 to rename the class.

Bug: 985616
Test: manual - Safe Browsing still works
Change-Id: I501e42b44d776f9be2f39a69bf4aa49a2209fc18
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1711217Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Auto-Submit: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: Richard Coles <torne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679588}

android_webview/apk/java/proguard.flags

@@ -68,12 +68,6 @@
     java.nio.channels.FileLock sExclusiveFileLock;
 }
 
-# Accessed via reflection but not present in all builds
--keep class com.android.webview.chromium.AwSafeBrowsingApiHandler {
-  AwSafeBrowsingApiHandler(...);
-}
--dontnote com.android.webview.chromium.AwSafeBrowsingApiHandler
-
 # We strip some unused resources when preprocessing the GMS client libs.
 -dontwarn com.google.android.gms.R**
 

chrome/android/java/monochrome_public_bundle.proguard_flags.expected

@@ -71,12 +71,6 @@
     java.nio.channels.FileLock sExclusiveFileLock;
 }
 
-# Accessed via reflection but not present in all builds
--keep class com.android.webview.chromium.AwSafeBrowsingApiHandler {
-  AwSafeBrowsingApiHandler(...);
-}
--dontnote com.android.webview.chromium.AwSafeBrowsingApiHandler
-
 # We strip some unused resources when preprocessing the GMS client libs.
 -dontwarn com.google.android.gms.R**