refactor: replace dh10application with a dynamic form builder schema

[fvcci]

There are several issues with the current database:

1. The dh10application table is not the application table for change ironically. What happens if a new form field is added? Or an old form field removed? There is no way to make the change without modifying the architecture of the database.
2. Form UI is hard coded. Some assumptions were made: the form's fields and its restrictions.

The proposed schema is as follows:

Some tasks to accomplish:

• implement the new schema
• refactor dh10application table queries to use the new schema
  • queries include submit, update, and application data retrieval

future roadmap:

1. reroute dh10application table to auto fill the current database OR migrate dh10application data to new schema
2. Remove codebase assumptions on the question's restrictions/conditions. database will indicate the restrictions on questions.
3. Remove codebase assumptions on the form's questions. All displayable question info will be provided by the database.
4. Cleanup legacy dh10application table

[fvcci]

Updating the schema. Removed the answers relation between Answer and FormSubmission tables and created a new relation between Answer and Users:

[fvcci]

Updating the schema. We want to have unique questions and answers for every form

AnswerType will be punted to a later issue.