namely:
  check_entities -> check_human_duplicates
  check_entity.js -> check_human_duplicate
  collect_entities -> collect_human_duplicates

laying ground for "delete" type tasks

this also renames the current "type" parameter to "entitiesType", this naming was here to avoid taking a decision about multi-words request parameters

this commit chose camel case, but next commit is the alternative kebab possibility

since actions are already using kebab

…ment

not only `{ "ok": true }`

since checkEntity has more complex results

threshold value is based on elastic score to create a defined amount of
tasks.

Its important to reject those suggestions after automerge, as a
conservative feature to not automerge too many tasks only based on
suggestions with a high lexical score, to not wrongly merge homonyms

to be able to later create deduplicate human tasks

makes a reposability separation between hooks and endpoint. It keeps couch view keys simple (not having byUrisAndbyStateAndByType) while restricts the endpoint access to stateless (aka not arcchived) tasks. This is possible since the client does not need to access archived tasks for the moment, so the new couch view only returns non-archived tasks.

which is currently not in use by the client, but leaving it since entity layout will actually reuse it to display its own related tasks one day