[Tech memo] Parser versioning

[andrew-jameson]

Description:
A work item from #3400 would be to approach versioning of the parser engine so we can more easily track changes such as new/modified/deprecated validators or differing error messages.

Acceptance Criteria:

• Technical memorandum that establishes a path forward on versioniong
• Testing Checklist has been run and all tests pass
• README is updated, if necessary

Tasks:

• Document any technical constraints, limitations, or challenges that may impact the implementation.
• Explore creating separate python package for schema_defs for versioning related to Enhance seed_db to be schema-aware and support versioning #3168
• Add versioning to records (t1 records, parserError, other objects).
• Run Testing Checklist and confirm all tests pass

Notes:

• Microservice app exploration?
• Separate git repo, divorced from TANF-app,
• versioning managed by DRF?

Supporting Documentation:

Open Questions: