Package version detection accepts any version as valid

Verified for executable version detectors

To reproduce:

1) In any JSON kit file (with an executable version detector, for example iar_nxp_mimxrt1050-evk-freertos.json), write any string in the "versions" field of a package with "versionDetection" and look at the packages in Edit>Preferences>Devices>MCU.

2) If there is no "validation"-field in the JSON, any existing path will be accepted.
If the "validation"-field is set to the executable listed in "versionDetection", an existing path *without* the executable will have the error message "<path> exists, but does not contain <executable> <version>". Here you can verify that it actually parses the (nonsensical) version string given in step 1

3) If you point to the correct path (the one containing the executable path given as "validation", the check turns green and the path is expected, even though the version clearly does not match

The consequences of this is that a user using an unsupported version of a dependency, will not be warned