dev-qt/qtbase: skip flaky tst_wayland_cursor in 6.10

Randomly had this fail then pass, test sounds timing related.
It's a small test case and probably not super important to check
here, so not going to worry about it. Unsure if even relevant
without a real wayland compositor and a cursor (offscreen).

For 6.9, this test was in dev-qt/qtwayland instead, albeit I
never had it fail there (yet) so will leave that alone.

Signed-off-by: Ionen Wolkens <ionen@gentoo.org>

dev-qt/qtbase/qtbase-6.10.9999.ebuild

@@ -356,11 +356,11 @@ src_test() {
 		tst_qsharedmemory
 		# typical to lack SCTP support on non-generic kernels
 		tst_qsctpsocket
-		# randomly fails without -j1, and not worth it over this (bug #916181)
-		tst_qfiledialog{,2}
-		# may randomly hang+timeout, perhaps related to -j as well
+		# flaky tests, may be better with -j1 but not worth using over this
+		tst_qfiledialog{,2} #916181
 		tst_qprocess #936484
 		tst_qtimer
+		tst_wayland_cursor
 		# haystacksWithMoreThan4GiBWork can easily OOM (16GB ram not enough)
 		tst_qlatin1stringmatcher
 		# these can be flaky depending on the environment/toolchain

dev-qt/qtbase/qtbase-6.9999.ebuild

@@ -356,11 +356,11 @@ src_test() {
 		tst_qsharedmemory
 		# typical to lack SCTP support on non-generic kernels
 		tst_qsctpsocket
-		# randomly fails without -j1, and not worth it over this (bug #916181)
-		tst_qfiledialog{,2}
-		# may randomly hang+timeout, perhaps related to -j as well
+		# flaky tests, may be better with -j1 but not worth using over this
+		tst_qfiledialog{,2} #916181
 		tst_qprocess #936484
 		tst_qtimer
+		tst_wayland_cursor
 		# haystacksWithMoreThan4GiBWork can easily OOM (16GB ram not enough)
 		tst_qlatin1stringmatcher
 		# these can be flaky depending on the environment/toolchain