#2184 - Add 'None' data type for enabling rule.min to accept input value.

[lainsworth8801]

Any background context you want to provide?

Data quality check minimum value is not enabled to accept input value when a new rule without a data type defaulted.

What's this PR do?

Added 'None' as one of the data types for rule.min to be enabled to accept user input values;
Removed 'null' from min and max to accept 0 values when saving rule settings.

How should this be manually tested?

Create a custom rule that is not listed in default rule list -> navigate to data quality tab and click 'create a new rule' -> in the drop-down value, select the custom rule -> as the data_type column is cleared, min value tab/form disappears not allowing any input.

What are the relevant tickets?

#2184

Screenshots (if appropriate)

[coveralls]

Coverage remained the same at 77.497% when pulling 613b900 on none_data_type_min into f18114e on develop.

[nllong]

@lainsworth8801 can you resolve these conflicts when you get a chance?

[lainsworth8801]

@lainsworth8801 can you resolve these conflicts when you get a chance?

Yes! Thanks for letting me know.

[adrian-lara]

Looking at the commits that were actual code changes (the ones that are not "Merge branch 'develop'..."), theses are the only two I see:

1. Removed null value for min and max to accept 0 value
2. Added 'None' data type for enabling rule.min to accept input value.

Both can be found in this PR