Returns the top-level food types supported by the unified mixed-intake contract and by GET /v2/food/search.

The types field contains every available top-level type:

• dish: a regular LogMeal dish;
• ingredient: an ingredient-only food item built from one or more recipe ingredients;
• favorite: a favorite owned by the target APIUser;
• custom_recipe: a custom recipe belonging to the target APIUser's APICompany;
• barcode_food_item: a previously resolved barcode product used as a complete food item.

These are the same top-level type discriminators accepted by POST /v2/intake/manualInput/USERID and the unified dishes contract of POST /v2/image/confirm/dish.

barcode_ingredient is not included because it is not a top-level food type. It is only valid as a nested recipe component inside another food item.

The query_required_types field identifies the types for which GET /v2/food/search requires a non-empty query.

Currently these are:

• dish
• ingredient
• barcode_food_item

favorite and custom_recipe can be requested through GET /v2/food/search without search text, allowing those private/template sources to be browsed directly.

If a /food/search request contains at least one type listed in query_required_types, a non-empty query is required.

This endpoint returns global contract information and does not depend on a target APIUser. Therefore, an APIUserManager does not need to provide user_id when calling this endpoint.