[docs] Should we start discouraging batching or at least not encourage it?

[leonhandreke]

From #957

Currently, I'm thinking that the ability to batch multiple queries in one request has maybe turned out to be one of the less successful decisions in the yente API design. For a few reasons:

1. it complicates the semantics, because now you have parameters that are per-request but your really want them per-query
2. we're running on Cloud Run and there the model is to run many small instances and scale up only if needed (which I understand is not what you're doing). So really, it would be better to have more requests of roughly equal weight come in instead of some that are really fat.
3. should be easy to do on the client, and that's less complexity on the server (but maybe I'm living too much in async unicorn land an in practice, people are working with much less nice language support on their clients?)

We could at least make the examples not contain batch queries. I'd prefer to actually discourage it somewhere in the docs. I feel like this is a change we can make without causing a commotion. One day, we'll have a v2 of the API, but that day is surely not now.

Somewhat related: #927

cc @goose-life

[pudo]

I'm not totally convinced that v2 of the API is not a this year kind of thing. Some ideas have been bundling up, such as:

• Moving stuff like the exclusion list in to the body
• Replacing the include_dataset, exclude_dataset, etc. thing with a DSL like datasets=default-(debarment|regulatory).
• Doing the same for dataset tags (maybe in the same DSL?).
• Getting rid of features etc.

Basically: much more of what we have now learned are sane defaults.