Further expand support for capture of student data and demographics by EducationOrganizationAssociation

Summary of outcomes for Data Standard 3.0

• Problem Addressed: Most of the properties previous included on the Student domain entity have been determined to be captured as a result of evaluation processes by LEAs, and therefore are subject to change, and subject to having different values if the student is enrolled at more than one LEA (e.g. if the student transfers or is dual-enrolled).
• High-level Reasoning: By relocating the properties in question, student data may be collected and stored in the context of their relationship with a particular EducationOrganization, most commonly the LEA.
• Changes Made: Relocate the remaining properties on Student to StudentEducationOrganizationAssociation (with the same cardinality) with the exception of the following properties, which will remain on Student:

• StudentUniqueId
• BirthData
• Citizenship
• Name
• OtherName

Original ticket description follows:
Some values that LEAs report differently (or could def be diff for LEA (e.g. electronicMail) that would justify removing from /student and adding to /studentEducationOrganizationAssociation:

ElectronicMail
Address
HispanicLatinoEthnicity
Race
Telephone
StudentIdentificationCode