Refactor attribute validation rules to use templates

[znatty22]

The current attribute validation rules come from the ingest library and they are specific to the Kids First data model (e.g. PARTICIPANT.GENDER must be one of Male, Female). We need to eliminate this hardcoded logic by constructing attribute validation rules from the template field definitions and then pass those into the validator.

[znatty22]

This probably won't be needed since we are incorporating a file mapping and in-line correction user flow. Attribute validation reports on the validity of values (e.g. range check, enum check, etc) and hopefully we will see less and less of these as users use the in-line correction functionality.