[Spike] - investigate how to toggle required listing fields by jurisdiction

[ludtkemorgan]

Bloom core (as well as HBA and Doorway) currently requires a large number of fields filled out on a listing in order to be published. This differs from the Detroit implementation where you can submit a listing with essentially no fields required. As Detroit gets applications we will need to make more fields required, however it will probably be a different set than what is used in core. This means that we will need to have a way to have different fields required based on the jurisdiction.

This spike is to figure out the following:

• What is the best way to toggle the different required fields?
  • One feature flag and they all come as a set?
  • An environment variable with a list of required fields?
• How do you handle different required fields on the backend?
• Do we need to do anything special on the partner frontend?

Notes:

• We already currently have different required fields depending on if it's a draft listing or published listing. Similar system could potentially be used.
• @sarahlazarich will be compiling a list of potential fields that will be required in Detroit and what is different in core

[sarahlazarich]

Potential for significant FE impacts
3 parts then - backend, public, partners
we have room to make a recc about what we can/can't require (whatever we need for apps)
see if there are any specific fields that are really hard to require or not