Remove unnecessary synchronization in `BazelBuildEventServiceModuleTest`.

This fixes occasional deadlocks in the test.

PiperOrigin-RevId: 416320729
diff --git a/src/test/java/com/google/devtools/build/lib/buildeventservice/BazelBuildEventServiceModuleTest.java b/src/test/java/com/google/devtools/build/lib/buildeventservice/BazelBuildEventServiceModuleTest.java
index ec9c6f0..22d9518 100644
--- a/src/test/java/com/google/devtools/build/lib/buildeventservice/BazelBuildEventServiceModuleTest.java
+++ b/src/test/java/com/google/devtools/build/lib/buildeventservice/BazelBuildEventServiceModuleTest.java
@@ -905,8 +905,14 @@
     @Nullable
     private String errorMessage = null;
 
+    /**
+     * Synchronizing this method can lead to deadlocks -- it calls into {@link
+     * io.grpc.inprocess.InProcessTransport} which takes a locks on itself. Opposite order of locks
+     * happens for {@link #publishBuildToolEventStream} called while holding the lock on {@link
+     * io.grpc.inprocess.InProcessTransport}.
+     */
     @Override
-    public synchronized void publishLifecycleEvent(
+    public void publishLifecycleEvent(
         PublishLifecycleEventRequest request, StreamObserver<Empty> responseObserver) {
       responseObserver.onNext(Empty.getDefaultInstance());
       responseObserver.onCompleted();