Change-Id: I1b6833b91ff0a23e32add3f32be975f66d5c365c
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>

On platforms running X11, windows are activated in an asynchronous
fashion. It is necessary to wait for the activation to happen using
primitives in the Qt Test library. This eliminates possible flakiness.
Such flakiness is seen on Ubuntu and OpenSuse.

Use QTRY_VERIFY instead of QVERIFY. This means that we wait five seconds
for window activation to happen.

Task-number: QTBUG-130374
Change-Id: I529b8d868bd3ecb5874ea8e9b950884ce1f8074e
Reviewed-by: Axel Spoerl <axel.spoerl@qt.io>
(cherry picked from commit 00e0461172ba0384f029d01ce93c2b6f30c406ae)
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>

Change-Id: Ibddce6be80c0cc1a920ffa0f66c5853dd41f1c10
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>

Blacklisting doesn't work since it times out.
Unblock CI until a fix can be found.

Task-number: QTBUG-132275
Task-number: QTBUG-132789
Change-Id: Ia162ced15ccf808fdde5d941406539ee4e6f84b9
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit 97bff2510d55a5174602e3dd2b839f46d4aaecc5)
Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>

Change-Id: I0ba1a643d319879bf6dc3f3d28b84a2ca8a114b2
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>

These versions are currently all over the board, and the intention is
to have them in line with the Qt for Android requirements (which is
Gradle 8.10 and AGP 8.6). Also update the Kotlin plugins while at it.

Task-number: QTBUG-132815
Change-Id: I72d8cb15d80b8b69301bbc2bbfeebf779ef137df
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
(cherry picked from commit 314c8eb4982e236d3b816a2cd688441d50c16acd)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit c27b4f71251782c4fd2102151fbee8b92f478554)

The findType() may determine that the target object is in a namespace.
Use the found type's qualified name rather than the name given in the
QML_FOREIGN declaration.

Fixes: QTBUG-132100
Change-Id: I1e8023a04fced64a5e6cd198ba7651712ee011e4
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
(cherry picked from commit 319aa02fe2bab08c2c91eb504237839d1448bf73)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit b6cdaf28ebabefdbdd6a99ec68e1a41f3b4e9fd5)

Implicitly constructing a value from a ReturnedValue muddies the
responsibility for ensuring that the gc can find the object.

With this change, we disable the implicit conversion. The expectation
for lifetime management is now:
- If a ReturnedValue is stored on the C++ stack, it must be put into a
  QV4::Scoped class (or there should be a comment why not doing so is
  safe). Passing a ReturnedValue to a function should no longer be
  possible, unless the function takes a ReturnedValue, in which case the
  expectation is that it stores the value in a place where it can be
  seen by the gc, before doing anything that could trigger a gc run.
  Using Value::fromReturnedValue can still be used to pass a Value on,
  but in that case, the expectation is that there is a comment which
  explains why this is safe.
- If a QV4::Value is obtained from a function call, it ought to be
  stored in a ScopedValue, too. We currently can't enforce this easily,
  so this should be checked during code review. A possible way forward
  would be to disallow returning Values, but that would be a larger
  change, and is deferred to the future.
- If a functions has a QV4::Value parameter, it's the callers'
  responsibilty to ensure that the gc can find it.

Pick-to: 6.5
Fixes: QTBUG-131961
Change-Id: Iea055589d35a5f1ac36fe376d4389eb81de87961
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
(cherry picked from commit a5feec81934ab0b074d6a8c7621b591851f6b544)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 64526c5e47a5f7217bced8f5affe29b5f1dc0c99)

... and delete it when not needed anymore.

While the preview service is inactive we don't need the file loader.
Since the file loader is rather heavyweight and comes with its own
thread, we should limit its life time.

Furthermore, it is suspected that the termination of the file loader
thread in the file loader's dtor triggers a bug that causes the debugger
tests to hang. Terminating the thread already on state change might work
around it.

Task-number: QTBUG-101678
Task-number: QTBUG-101972
Task-number: QTBUG-102984
Task-number: QTBUG-132697
Change-Id: I244aa4c3d4257f0c4b8f46f826710a76cf389baa
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit 529491f6dc8d0d49129333861c7812ce4931dc69)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 4fdef30fe1dc21555df347d67bebe063b39f7a01)

QVariantList does not have to be stored as literally Array, an
array-like that we also use in so many other places is entirely
adequate. Furthermore, you can update QVariantList properties in place
these days.

Pick-to: 6.5
Task-number: QTBUG-125289
Change-Id: Iacf45579b1db31d7644259f9a0e46e595fe7ecfc
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit 892fbeffe23afb3ce0a48ca8357e18f14db649e9)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
(cherry picked from commit 6e3ef191c615b1ef1983d9a6421f0ee36d93b71c)