Add a content takedown policy and mechanisms, including contact method

[jayaddison]

Is your feature request related to a problem? Please describe. Although recipe images and domain icons have been temporarily removed from the site, we hope to restore these at some point if that becomes an acceptable consensus for content publishers and site users alike.

Before then, it'd be worth adding a content takedown policy in case there are any situations where an individual publisher would prefer for their content to be removed.

Describe the solution you'd like

• [x] A mechanism to disable images and/or recipe search results for a given domain (edit: removed recipe requirement; background/context here)
• [x] A mechanism to remove an individual image and/or recipe (edit: removed recipe requirement; background/context here)
• [ ] A published audit log of the removals, if that is reasonable

Describe alternatives you've considered It is currently possible to contact us via the feedback form, and we can take down content if asked. It would be better to have a transparent and managed process for this.

[jayaddison]

Thumbnail images have been back on the site as of 2022-06-16.

Perhaps it'd be reasonable to argue that the partial form of recipes that we display -- only the post-processed ingredient list, and not any of the steps/instructions involved -- could be legally acceptable as they are, meaning that how to deal with potential takedown requests for thumbnail images is the most important item to handle.

I'll update the solution description based on that.

[jayaddison]

Thumbnail images have been back on the site as of 2022-06-16.

Note: thumbnail images were subsequently disabled again by default on 2022-11-17 and have remained inactive since then (ref: https://github.com/openculinary/image-retrieval/issues/8 ).