The development site recipe gives media and facet fields the wrong types

Problem/Motivation

The recipe the module is developed against declares several fields with a different type from the sites the code was written for. The code reads those fields the way the sites store them, so on the development site four listing and detail endpoints answer with a fatal error instead of a payload:

• field_facets references taxonomy terms, and on thirteen node bundles; the sites reference myfacet entities from the bundle that holds the listing settings. MyfacetManager::normalizeMyfacets() calls isActive() on what it gets and fatals on a term.
• field_article_image, field_doctor_photo and field_photo_preview are image fields; on the sites they reference media of the image type, and field_doctor_certificates, field_doctor_photos and the term field field_main_img — media as well — are missing altogether.

A development site whose model differs from the one the code expects tests neither: the errors hide every key behind them, and a green run on it says nothing about a real site.

Proposed resolution

• Give these fields the types, cardinalities and bundles the sites use, and fill them: media of the image type with real files, myfacet entities — with the characteristics they point at — referenced from the bundles that hold listing settings.
• Add a check that compares the field storages the recipe creates with a list taken from the sites' configuration, so that the types cannot drift again unnoticed.
• Verify on the endpoints themselves: every endpoint that fatals today answers with a payload whose facet and image keys carry values.

Remaining tasks

Everything.