Description:
Using the tech memo outlined in #3452 as a guide, refactor the parsing engine from the functional design to the recommended class based design. No work on the FRA parser outlined in the tech memo should be included in this work. Only current parsing code should be refactored.

Acceptance Criteria:
Create a list of functional outcomes that must be achieved to complete this issue

• Class based parser implemented
• All current parser tests do not change logically
• Testing Checklist has been run and all tests pass
• README is updated, if necessary

Tasks:
Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue

• Update the SchemaManager to handle context for entire file
• Implement suggested decoder class hierarchy
• Implement parser class and subclass
• Update parse logic to leverage new class
• Run Testing Checklist and confirm all tests pass

Notes:

• I wanted to see if there was any naming guidance we could use to aggregate TANF/SSP/Tribal with one term since we have FRA as a concise term. I asked Kathryn and this was the response: Just spoke with Alex. Internally they sometimes refer to these files as TDR - TANF Data Report. The implementer can use this info as they see fit.