Support specifying a minimum required AT version in the name of a commands.csv file

[mcking65]

We have now encountered a scenario where a new version of a screen reader changed its commands. PR #1020 added new instructions for quick nav settings. This means that there is now a minimum required version of macOS required for all VO test plans.

Going forward, we could encounter more scenarios like this. It could also be the case that a new version of an AT is released and we need the ability to run tests for both the older versions and the new version.

We could handle scenarios like this if the commands file specified the versions of an AT for which it is applicable. One possible approach is that the commands file file name specifies the minimum version required. For example:

voiceOver_macOS+14.3-commands.csv

Then, if a run in the test queue specifies either a minimum version of 14.3 or a version that is newer than 14.3, the test runner would use that commands file. Similarly, in the reports, the commands shown would match the version requirements specified by the commands file.

For backward compatibility, if there are multiple files for the same AT and one does not specify a minimum version, it would be assumed to be applicable to versions that are older than the version specified by the file with the earliest minimum version.

The version numbers specified would need to exactly match the version numbers specified in the version list in the app.

To be completely robust, the version numbers specified in the app should have approximate release dates so versions can be reliably sequenced in time.