Deprecate meta in favor of aggregation

[azrikahar]

Deprecate metadata from the api (and existing usages in the app) in v10 in favor of aggregation such as aggregate[count]. Originally planned back in #5880.

[benosman]

Would this lose the ability to get both the collection items and the filter_count in one api request?

I know on the DB side metadata involves an extra query, but it is handy when using the REST API to save a roundtrip by getting the metadata in the same response.

Is there any way to do to this with aggregate[count]?

[rijkvanzanten]

@benosman If we'd want to keep it REST "proper", doing one query per request is correct. GraphQL has the benefit of doing multiple queries per request. That being said, I'm down to figure out if there's a clean way we can allow both aggregating and regular data fetching simultaneously

[rijkvanzanten]

Linear: ENG-185

[jaads]

the actual removal of the mata attribute in the API response is currently on hold.

we will first mark this as deprecated in the docs and do the actual breaking change later.