Don't implement ForwardingLb.acceptResolvedAddresses()

Any old implementations that still implement handleResolvedAddresses()
will have their implementationed "skipped" by new callers of
acceptResolvedAddresses(). We've been having such forwarders implement
both methods instead. Since there's very few usages of
handleResolvedAddresses() left, out-of-tree implementations should
generally be fine just swapping to acceptResolvedAddresses.

Author: ejona86

util/src/main/java/io/grpc/util/ForwardingLoadBalancer.java

@@ -29,22 +29,11 @@ public abstract class ForwardingLoadBalancer extends LoadBalancer {
    */
   protected abstract LoadBalancer delegate();
 
-  /**
-   * Handles newly resolved addresses and metadata attributes from name resolution system.
-   *
-   * @deprecated  As of release 1.69.0,
-   *     use instead {@link #acceptResolvedAddresses(ResolvedAddresses)}
-   */
   @Deprecated
   public void handleResolvedAddresses(ResolvedAddresses resolvedAddresses) {
     delegate().handleResolvedAddresses(resolvedAddresses);
   }
 
-  @Override
-  public Status acceptResolvedAddresses(ResolvedAddresses resolvedAddresses) {
-    return delegate().acceptResolvedAddresses(resolvedAddresses);
-  }
-
   @Override
   public void handleNameResolutionError(Status error) {
     delegate().handleNameResolutionError(error);

util/src/test/java/io/grpc/util/ForwardingLoadBalancerTest.java

@@ -20,6 +20,7 @@
 
 import io.grpc.ForwardingTestUtil;
 import io.grpc.LoadBalancer;
+import io.grpc.LoadBalancer.ResolvedAddresses;
 import java.util.Arrays;
 import org.junit.Test;
 import org.junit.runner.RunWith;
@@ -43,7 +44,7 @@ public void allMethodsForwarded() throws Exception {
         LoadBalancer.class,
         mockDelegate,
         new TestBalancer(),
-        Arrays.asList()
-    );
+        Arrays.asList(
+            LoadBalancer.class.getMethod("acceptResolvedAddresses", ResolvedAddresses.class)));
   }
 }