Revert "Opt into base::ThreadPriority::DISPLAY for all ozone builds"

On targets without a display (is_cast_audio_only), increasing the
priority is not justified and reduces the bandwidth available to audio
processing threads.

This may be causing audio input overruns on certain devices, so back it
out for now.

This reverts commit df1aafa964c2ad1b8342d691828dea643a201d53.

Bug: b/126796692

Change-Id: I654c1759d68a56e0cc8e4b7a276484b47aa379f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1682750
Commit-Queue: Michael Spang <[email protected]>
Reviewed-by: Jeremy Roman <[email protected]>
Reviewed-by: Antoine Labour <[email protected]>
Reviewed-by: Sunny Sachanandani <[email protected]>
Cr-Commit-Position: refs/heads/master@{#674216}
diff --git a/gpu/config/gpu_finch_features.cc b/gpu/config/gpu_finch_features.cc
index c5a7732b..66675ae1 100644
--- a/gpu/config/gpu_finch_features.cc
+++ b/gpu/config/gpu_finch_features.cc
@@ -75,7 +75,7 @@
     "DirectCompositionUnderlays", base::FEATURE_ENABLED_BY_DEFAULT};
 
 // Use ThreadPriority::DISPLAY for GPU main, viz compositor and IO threads.
-#if defined(OS_ANDROID) || defined(OS_CHROMEOS) || defined(USE_OZONE)
+#if defined(OS_ANDROID) || defined(OS_CHROMEOS)
 const base::Feature kGpuUseDisplayThreadPriority{
     "GpuUseDisplayThreadPriority", base::FEATURE_ENABLED_BY_DEFAULT};
 #else