[VxWorks] Recover from guest resets instead of running unprovisioned
A VxWorks guest that hits a kernel exception reboots itself. QEMU
then restarts the kernel from the same -kernel/-append, and the guest
comes back running only the romfs startup script, without the
per-instance configuration written over the serial console by
coin_vxworks_vars.sh. The test runner's health check (serial echo and
SSH rtp list probe) cannot tell such a guest from a healthy one, so it
keeps handing tests to it. In a qtdeclarative run one x86 emulator
slot rebooted about 90s after provisioning and then failed every test
it was given, because the startup script set an LD_LIBRARY_PATH with
the ARM VSB path baked in, so no RTP could load its shared objects.
Fix both halves:
Start QEMU with -no-reboot, so a guest reset ends the QEMU process
instead of rebooting the kernel. The runner already detects a dead
emulator (serial FIFO without a reader, SSH unresponsive) and
relaunches and re-provisions that slot only; the other parallel
instances are unaffected. A reset during boot is now reported by the
launcher's "exited during boot" check right away instead of after
the SSH wait deadline.
Update the VSB and VIP images to build 15-09-2026, whose startup
script sets the correct per-architecture LD_LIBRARY_PATH, so a guest
that does come up from the romfs defaults is still able to run RTPs.
Fixes: QTBUG-150258
Pick-to: 6.12
Change-Id: I199c507eae14a54c6765f3166a56236c44782f1b
Reviewed-by: Toni Saario <toni.saario@qt.io>