The connectivity test fails on a QNX device

Description:

When running the device test in Qt Creator for a QNX device, the test fails if certain tools are missing, but the error reporting does not indicate the root cause.

Currently, if required tools such as base64, mktemp, or mkfifo are missing on the device, Qt Creator displays only:
Connecting to device... Basic connectivity test failed, device is considered unusable. Device test failed.
 
There is no clear indication of which specific tool is missing or causing the failure. This makes troubleshooting unnecessarily difficult.

Documentation improvements:

The Qt Creator documentation currently states:

"The board support package (BSP) for the QNX device might be missing some of the following applications that Qt Creator needs to run, debug, and stop applications on QNX devices: awk, grep, kill, netstat, print, printf, ps, read, sed, sleep, uname, slog2info, and cat."

• The documentation does not mention that base64, mktemp, and mkfifo are also required for device test functionality.

• The mkfifo requirement should be explicitly documented, along with a note that in QNX systems, mkfifo does not work if /tmp is mounted as a ramdisk. Using ramdisk for temporary files is common on embedded devices to improve performance and reduce flash wear.

• If a ramdisk is used for the temp folder, a proper error should be shown when mkfifo fails.