Implement Requirements SCH2006 and SCH2007

[ArielSAdamsNASA]

Checklist (Please check before submitting)

• I reviewed the Contributing Guide.
• I performed a cursory search to see if the bug report is relevant, not redundant, nor in conflict with other tickets.

Is your feature request related to a problem? Please describe.
Requirements SCH2006 and SCH2007 are not implemented.

Describe the solution you'd like
SCH2006: Upon receipt of a SDT Load, SCH shall validate the entries of the table and if any entry is invalid, the table is declared invalid and rejected.
SCH2006.1: SCH shall identify any "Unused" SDT entry that contains data other than "Unused" as invalid
SCH2006.2: SCH shall identify any "Enabled" or "Disabled" SDT entry that contains a Frequency of zero as invalid
SCH2006.3: SCH shall identify any "Enabled" or "Disabled" SDT entry that contains a Frequency Offset greater than the entry's specified Frequency as invalid.
SCH2006.4: SCH shall identify any "Enabled" or "Disabled" SDT entry that contains a Message Index of zero or greater than the maximum number of Messages in the Message Definition Table as invalid.
SCH2006.5: SCH shall identify any "Enabled" or "Disabled" SDT entry that contains an undefined Activity Type as invalid.

SCH2007: Upon receipt of a Message Definition Table Load, SCH shall validate the entries of the table and if any table entry is invalid, reject the table
SCH2007.1: SCH shall identify any "Unused" MDT entry that contains data other than "Unused" as invalid
SCH2007.2: SCH shall identify any MDT entry that has a message definition with a Message ID that is greater than <MISSION_DEFINED> maximum Message ID as invalid
SCH2007.3: SCH shall identify any MDT entry that has a message definition with a Message ID that is less than <MISSION_DEFINED> minimum Message ID as invalid
SCH2007.4: SCH shall identify any MDT entry that has a message length greater than <PLATFORM_DEFINED> maximum message length as invalid
SCH2007.5: SCH shall identify any MDT entry that has a message length that is an odd number of bytes as invalid

Additional context
It looks as though this requirement is being met in SCH_AcquirePointers - it's handling table loads through table services during the housekeeping cycle, not through an explicit command. The sub-requirements are not being met.

Reporter Info
Ariel Adams, MCSG Tech