feat: add a restriction table to the questions in the new applications database

[fvcci]

A refactor of the code should look something like this:

Comprehensive refactor for improved maintainability

The current implementation, while functional, is repetitive and could be challenging to maintain as the application grows. Consider a more scalable approach by defining the form structure declaratively and rendering it dynamically.

Here's a high-level suggestion for refactoring:

1. Define a structure that represents your form:

const formStructure = [
  {
    category: "Personal Information",
    fields: [
      { type: "input", id: "firstName", placeholder: "John" },
      { type: "input", id: "lastName", placeholder: "Doe" },
      // ... other fields
    ]
  },
  {
    category: "Education",
    fields: [
      { type: "checkbox", id: "isStudent" },
      { type: "input", id: "school", placeholder: "School...", conditional: "isStudent" },
      // ... other fields
    ]
  },
  // ... other categories
];

2. Create a function to render fields based on their type:

const renderField = (field, index, categoryIndex) => {
  const { type, id, placeholder, conditional } = field;
  const { question, answer } = getQuestionAnswer(index, categoryIndex);
  
  if (conditional && !getQuestionAnswer(conditional, categoryIndex).answer) {
    return null;
  }

  switch (type) {
    case "input":
      return <FormInput key={id} label={question} text={answer} placeholder={placeholder} />;
    case "checkbox":
      return <FormCheckbox key={id} label={question} checked={answer === "true"} readOnly />;
    // ... handle other field types
  }
};

3. Render the form using the structure:

{formStructure.map((category, categoryIndex) => (
  <div key={category.category}>
    <FormDivider label={category.category} />
    {category.fields.map((field, index) => renderField(field, index, categoryIndex))}
  </div>
))}

This approach would significantly reduce code duplication, improve maintainability, and make it easier to add or modify form fields in the future.

Originally posted by @coderabbitai[bot] in #191 (comment)