Check required versions of dependencies when creating MCU kits

Required versions of the dependencies

Right now, the kit generation only checks that the required executables are available at the expected paths.
However, the versions of the tools are not checked.

This task is to:

1. Find out which versions are required for each dependency
2. Figure out at which point in the process the version should be checked (probably when checking that the path to the dependency is valid)
3. Create the functionality for such check (if possible)
4. Displaying problems to the user (in the Dialog Ui as well as the General Messages output)

Current dependencies of the different kits supported by the MCU plugin:

• Armgcc
• Green Hills Compiler
• IAR Arm Compiler
• gcc
• Microsoft Visual C++ Compiler
• STM32 Cube Programmer
• McuXpresso IDE

The 'legacy' function for the targets Baremetal and FreeRTOS also depend on:

• Renesas Graphics Library

Update:

• The kit description files distributed together with Qt for MCUs contain version numbers for the toolchains (e.g. armgcc) and the sdks.  We can use that for checking the versions.
• Some of the dependencies are not explicitly in the description files (e.g. that's the case for the McuXpresso IDE).  For this task, we only check the dependencies where the version is in the description.  Hard-coding versions in the code of the plugin is to be avoided.
• While working in this task, we should check how the Qt for MCUs build process checks those versions, and that all toolchains and sdks will have them in the description files.
• If a version of an installed dependency is below that found in the description file, we're to show a warning only, but let the kit creation process continue.