Qt Creator should attempt to preserve custom build steps on shared project settings

Shared project settings can't be used to deploy custom build steps as a template to different machines. These will be preserved only if the ProjectExplorer.ProjectConfiguration.Id stored in the .pro.shared file is the same of one of the kits installed in the machines. This is limiting in projects where the build steps are fully custom, as in my case (I'm using an hybrid cmake/qmake system to workaround various limitations in using cmake build system only). By comparison with Visual Studio, msbuild build system (which of course has much wider purpose) allows for unrestricted customization of the build process and it can be deployed because it's not an user setting. This has been requested other times, QTCREATORBUG-8744, QTCREATORBUG-15132, QTCREATORBUG-8325, with above bugs closed as invalid citing limitations in preserving automatic qmake build steps that contains machine specific paths/settings (which, if limited to paths, seems to be an original bad design choice). Without asking for the full customizability of msbuild, I suggest Qt Creator could offer limited support for templatization of build steps by preserving them when the line <value type="QString" key="ProjectExplorer.ProjectConfiguration.Id">...</value> is not present in the .shared.pro file. In this way it would be explicit that the build steps are not specific for any kit. Of course it's in the responsibility of the uploader of the .pro.shared file that the commands are portable in the target machine. This would save the final develeoper from fully refilling the GUI with actual build steps, that is tedious and may also be complex.

Attached sample project with (not working) shareable build commands steps.