use SendContext to ensure no goroutine leaks

Author: easwars

xds/internal/xdsclient/tests/ads_stream_ack_nack_test.go

@@ -64,10 +64,7 @@ func (s) TestADS_ACK_NACK_Simple(t *testing.T) {
 			return nil
 		},
 		OnStreamResponse: func(_ context.Context, _ int64, _ *v3discoverypb.DiscoveryRequest, resp *v3discoverypb.DiscoveryResponse) {
-			// The go-control-plane management server continuously resends the
-			// same resource if NACKed by the client. Hence, we need to use
-			// `Replace` here instead of `Send`.
-			streamResponseCh.Replace(resp)
+			streamResponseCh.SendContext(ctx, resp)
 		},
 	})
 
@@ -246,7 +243,7 @@ func (s) TestADS_ACK_NACK_InvalidFirstResponse(t *testing.T) {
 			return nil
 		},
 		OnStreamResponse: func(_ context.Context, _ int64, _ *v3discoverypb.DiscoveryRequest, resp *v3discoverypb.DiscoveryResponse) {
-			streamResponseCh.Send(resp)
+			streamResponseCh.SendContext(ctx, resp)
 		},
 	})
 
@@ -351,7 +348,7 @@ func (s) TestADS_ACK_NACK_ResourceIsNotRequestedAnymore(t *testing.T) {
 			return nil
 		},
 		OnStreamResponse: func(_ context.Context, _ int64, _ *v3discoverypb.DiscoveryRequest, resp *v3discoverypb.DiscoveryResponse) {
-			streamResponseCh.Send(resp)
+			streamResponseCh.SendContext(ctx, resp)
 		},
 	})