SESI-223: protobuf messages for validation and ValidateCommandOptions review and impl
protobuf messages updated. ValidationResults updated (to have rules map). REST endpoints for starting validation and retrieving results implemented and working
Adding GWT changes (preliminary, not functional yet)
Refactored validators into constraints. Added embedded vocabulary support.
Adding MinValue, MaxValue and PastDate data constraints with unit tests. Improving the detail of validation failure messages
Adding ConstraintType constant (forgotten from previous commit)
Improving the validation messages adding entity id
Adding validation REST resources, protobuf messages and transaction support from previous branch
Python tool to trigger validation (incomplete)
TableValidation* is now a perfect clone of ValuesTable*, for testing pusposes
Temporary impel using ValuesTable tab for validation. REST validation job scheduling and results retrieval is working
Validation results are being displayed (still in temporary location)
Validation results are now cleared when a new table is selected. Improved the location of Validate button
Adding colors to validation overview cells
Removing opal-python tool to launch validation (no longer needed)
Now validation job completion is properly polled. ValidateCommand returns a proper empty result when no validation is enabled
Small fixes and adjustments. Now validation just needs to be moved to the proper tab
Added handling for error states. Solved bug on method ValuesTableView.needsValidationViewReset
fixed problem with invisible validation tab
Validation tab is now complete