OzoneImageBacking - Remove unused workaround for fences on Mali

The workaround for caching GL textures was extended from freedreno
drivers to all Mali drivers. With that workaround we don't need a
separate workaround for adding fence on same gl context as there is
only one gl texture being read from and written to for a representation.

Bug: 1350094
Change-Id: Ifaa2eeeb9c36ffbd78a66f6a14526539bc5f52f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3900733
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Saifuddin Hitawala <hitawala@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1051202}

gpu/command_buffer/service/shared_image/ozone_image_backing.cc

@@ -426,9 +426,8 @@ bool OzoneImageBacking::BeginAccess(bool readonly,
   }
 
   // If current stream is different than `last_write_stream_` then wait on that
-  // stream's `write_fence_` (except on ARM Mali boards for ChromeOS).
-  if (!write_fence_.is_null() && (workarounds_.add_fence_for_same_gl_context ||
-                                  last_write_stream_ != access_stream)) {
+  // stream's `write_fence_`.
+  if (!write_fence_.is_null() && last_write_stream_ != access_stream) {
     DCHECK(external_write_fence_
                .is_null());  // `external_write_fence_` should be null.
     // For write access we expect new `write_fence_` so we can move the old

gpu/config/gpu_workaround_list.txt

@@ -1,5 +1,4 @@
 add_and_true_to_loop_condition
-add_fence_for_same_gl_context
 adjust_src_dst_region_for_blitframebuffer
 avoid_one_component_egl_images
 avoid_stencil_buffers