Improve Settings values validation

[ferpasri]

1. Extend the default TESTAR settings validation that only parses the value of different settings (Double, Integer, Boolean, etc.)

To additionally validate if the users are providing correct input values for the different groups of settings:

• AbstractStateAttributes validate custom state tags for state abstraction
• ApplicationName validate special characters that affect output results creation
• ClickFilter validate regex expressions

2. Add webdriver CI test for Linux and macOS

3. Bug fixing:

   • If SUTConnectorValue is empty, show a message and finish the main process
   • Fix Android Spy mode screenshot

4. Update selenium and Dockerfile dependencies