Completely ignore locking ordering when trylock is involved, as that is safe

tools/valgrind/starpu.suppr

@@ -81,9 +81,8 @@
 {
    mc / handle locking order. We always take handle before mc, except when we tidy memory, where we use trylock, but helgrind doesn't handle that :/ https://bugs.kde.org/show_bug.cgi?id=243232
    Helgrind:LockOrder
-   ...
+   fun:mutex_trylock_WRK
    fun:__starpu_spin_trylock
-   fun:lock_all_subtree
    ...
 }