Show detailed kit info in error cases

It would be good to send information to the user if a kit is defunct and what they should do there.

Consider iOS case: You download iOS kit with Qt and decide to try out your app on your new iPhone? All goes well. 

Fire up Creator afterwards, select a project and run cmake (happens automatically) and after some time you have:

Yay, I am ready to compile. Let's go. Click on the hammer (slightly wondering why the 'Play' icon is not lit but should not be bothered maybe?

Click on the hammer and things start to progress.... until

Okay, what now? I doubleclick on the error - and nothing.

So, here are the suggestions:

• if the compile process fails, we kinda know the root causes and have pointed out these into the documentation. We should tell in the error cases WHICH doc you have to read to proceed, not "read the doc" or anything alike.
• If the 'Play' or 'Build' icon is not lit on the Creator, we could point the user to read correct docs when user hovers on the disabled icon. I'm sure all kits have their own things the kit itself needs - which are self-explanatory to us or any Qt ecosystem member but a person from 'out there' will drop the hammer immediately.

Better UX in this case would be that the "Xcodebuild failed" would be instead: XCodebuild failed, please see https://doc.qt.io/qt-6/ios.html for known issues with Qt on iOS"

Great UX would be that if you doubleclick the error it would tell that 'We could not run XCodebuild for some reason, maybe your Xcode setup with this device is not set up yet? Please check our wiki page <url> for known issues with this kit. If the problem does not get fixed, feel free to reach out to our support <chat/number>. If you consider this is a bug in the system, feel free to generate an error report <jira-link with all right metadata prefilled>".

Also