Figure out how to version forms and registration applications

[BCerki]

Describe the task

When users apply to register, we need to save their point-in-time data and the point-in-time forms so that the historical record can be viewed later.

This means versioning of:

• rjsf json schema
• rjsf ui schema? (it doesn't seem to break the FE to have unused fields in the schema, but it does get messy)
• django ninja schemas (giraffe is skipping these entirely) => Sep: How can we ensure that the incoming data is valid?
• maaaaybe models if there are massive changes

Some options and notes:

• Giraffe is using config models to generate their json schemas. Their forms are much more complicated than Moose's though
• something to create a schema straight from the actual (vs. a config) model, e.g. the facility form jsonSchema is generated based on the fields in the facility model
• the single-step task list requires the sections to be hardcoded into it, which means we have to do transformation going in and out, or we change this

Acceptance Criteria

• [ ] first
• [ ] second
• [ ] third

Additional context

• Add any other context about the task here.
• Or here

[hannavovk]

Dev discussion needed

[andrea-williams]

Dev discussion June 25: decided that form versioning is not necessary in the immediate future; may not be necessary at all. Likely requires further discussion with biz area. Iceboxing this for now so we can unblock several user stories.