Add server side validation to be consistent with client side validation

[mmurthydol]

Validation must be consistently implemented both at the UI and API level. This indirectly also helps with security.

Acceptance Criteria

Ensure that all API calls that accept input parameters are validated if those parameters contain data from client side fields that have validation performed against them.

• [ ] All Required validation (server side) must be consistent with client side required validation.
• [ ] All Required Validation (server side) must also be type consistent with data type expected. Ex: entered number when number was expected or not? Is Data truncated? Date?
• [ ] All Range validation (server side) must be consistent with client side range validation. Ex: If number entered needs to be > 0; < some_integer. 14C online client side is currently using <, > and not <=, >= !!!
• [ ] Email RegEx validation: regex = /^[-a-z0-9~!$%^&_=+}{'?]+(.[-a-z0-9~!$%^&=+}{'?]+)*@([a-z0-9][-a-z0-9]*(.[-a-z0-9]+)*.(aero|arpa|biz|com|coop|edu|gov|info|int|mil|museum|name|net|org|pro|travel|mobi|[a-z][a-z])|([0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}))(:[0-9]{1,5})?$/i
• [ ] EIN RegEx validation: regex = /^\d{2}-\d{7}/;
• [ ] Zip code RegEx validation:
  regex = /^[0-9]{5}(?:-[0-9]{4})?$/i; Won't work for int'l addresses!!!
• [ ] Phone RegEx validation: regex = /^(+\d{1,2}\s)?(?\d{3})?[\s.-]\d{3}[\s.-]\d{4}$/; Won't work for int'l numbers!!!
• [ ] Certificate Number RegEx Validation: regex = /(\d{2}-\d{5}-[S,H,E,P]-\d{3})/

[PrabhakarThummalaDOL]

Completed.