[SYCL] Avoid overuse of CPU on wait read-write lock loop (#2525)

The while loop in lockSharedTimedMutex causes 100% usage of CPU
if host application generates command groups in multiple threads
That slow downs overall execution.

Author: vladimirlaz

sycl/source/detail/scheduler/scheduler.cpp

@@ -12,9 +12,11 @@
 #include <detail/scheduler/scheduler.hpp>
 #include <detail/stream_impl.hpp>
 
+#include <chrono>
 #include <memory>
 #include <mutex>
 #include <set>
+#include <thread>
 #include <vector>
 
 __SYCL_INLINE_NAMESPACE(cl) {
@@ -268,7 +270,11 @@ void Scheduler::lockSharedTimedMutex(
   // TODO: after switching to C++17, change std::shared_timed_mutex to
   // std::shared_mutex and use std::lock_guard here both for Windows and Linux.
   while (!Lock.owns_lock()) {
-    Lock.try_lock();
+    Lock.try_lock_for(std::chrono::milliseconds(10));
+    // Without yield while loop acts like endless while loop and occupies the
+    // whole CPU when multiple command groups are created in multiple host
+    // threads
+    std::this_thread::yield();
   }
 #else
   // It is a deadlock on UNIX in implementation of lock and lock_shared, if