Improve error handling when validating constraints

[npatki]

Problem Description

In the new version of SDV 1.0, I will be able to provide constraints using a dictionary format such as:

{
  'constraint_class': 'Inequality',
  'table_name': 'hotel_logs', # required for multi table
  'constraint_parameters': {
    'low_column_name': 'start_date'
    'high_column_name': 'end_date'
  }
}

Currently, there is a confusing errors if I don't provide the constraint_parameters key:

InvalidConstraintsError: The provided constraint is invalid:
Missing required values {'column_names'} in a CustomConstraint constraint.
'NoneType' object is not iterable

Expected behavior

We should explicitly check for the following:

• In a multi table case, the top-level dictionary keys should be 'constraint_class', 'constraint_parameters' and 'table_name'
• In single table, the top-level dictionary keys should be 'constraint_class' and 'constraint_parameters'

If the required top-level keys are not found, throw the following error:

SynthesizerInputError: A constraint is missing required parameters (<missing values>). Please add these parameters to your constraint definition.

Example:
SynthesizerInputError: A constraint is missing required parameters ('constraint_class'). Please add these parameters to your constraint definition.
SynthesizerInputError: A constraint is missing required parameters ('constraint_parameters', 'table_name'). Please add these parameters to your constraint definition.

If there are extra keys that are found, throw the following error:

SynthesizerInputError: Unrecognized constraint parameter (<example>). Please remove this parameter from your constraint definition.

Example
SynthesizerInputError: Unrecognized constraint parameter ('column_name'). Please remove this parameter from your constraint definition.