Better UX for mapping form inputs to eligibility checks

Originally surfaced by #357

There is a "chicken or egg" issue when creating the form and sometimes you want to focus on the questions and sometimes you want to focus on ensuring all eligibility checks are accounted for.

## Idea:
Allow the user to toggle between "modes". One mode where the eligibility checks are less emphasized but with a way to validate mapping t to form inputs (this is the current functionality in `main` branch) and another mode where that is focused on the eligibility checks with the form possible form inputs that could be implemented for them (this is the concept presented in #357).

This could take the form of two different tabs in the "Components" section of the form editor; one that shows all components, the other that allows you to select/map only the components that are possible for a given (selected) eligibility check.