Add error checking to building a test

[abacef]

Is your feature request related to a problem? Please describe.
When I or a user of the GUI test builder builds a test that does not appear to work correctly on the instrument

Describe the solution you'd like
It may be a cool idea to have there be some sort of validation of numbers or string regular expressions for sending data to instruments. On most of the instruments I tested, if a command is invalid, the instrument just wont do anything. Some instruments set an error code if an invalid command is entered. Right now, on the PTCS side, there is no error detection or acknowledgement. Here are some options on how to make this better:

• Make the driver have every command sent also query the instrument for if the command sent was valid. If it was not, you can do things with raising exceptions in the driver. I would not advocate this because it can be mission critical to have some commands operate at their max speed, and this data communication overhead can be really slow
• Each query command can have a validation command called on its parameters and if when the query command is called in the driver, raise an exception to the user before the command is tried. This can be time consuming for someone writing a driver to find and successfully implement a robust validator for each method
• When a test is built, before the file gets saved, call the validation methods on each command input and tell the user if there were any errors and what they are so the user can successfully save the test. Catching the errors before run-time if possible is always good.

Describe alternatives you've considered
Debugging the issue by hand

Additional context
None