Report problems with the requirements a search ran on rather than with a profile:
a requirement that is ambiguous, bundles several conditions, has the wrong
must-have setting, was added although the request did not ask for it, or misreads
the request, plus what the request asked for that no requirement covers.
Identify the search with the /v2/search response's thread_id and, optionally,
its uuid as search_id. flags[].requirement_index is the position of a
requirement in search_requirements_stats; Pearch stores a snapshot of those
requirements with the feedback and returns it as requirements.
There is one entry per thread and each submission replaces it, whoever sends it.
Requirements without codes or a note are not stored.
400Invalid values, unknown codes, or a requirement index outside the search's requirements
401Invalid API key
403Invalid API key
404No completed search in the thread, or none with this search_id
