Paginated delete (fixes #987)

[leplatrem]

Fixes #987

• Add limit/sorting to querystring
• Add next-page header to plural delete responses
• Plug model resource models
• Add necessary parameters to storage backend
• Check out documentation

[Natim]

     :param filters: Optionally filter the records by their attribute.
         Each filter in this list is a tuple of a field, a value and a
         comparison (see `kinto.core.utils.COMPARISON`). All filters
         are combined using *AND*.
     :type filters: list of :class:`kinto.core.storage.Filter`

     :param sorting: Optionnally sort the records by attribute.
         Each sort instruction in this list refers to a field and a
         direction (negative means descending). All sort instructions are
         cumulative.
     :type sorting: list of :class:`kinto.core.storage.Sort`

     :param pagination_rules: Optionnally paginate the list of records.
         This list of rules aims to reduce the set of records to the current
         page. A rule is a list of filters (see `filters` parameter),
         and all rules are combined using *OR*.
     :type pagination_rules: list of list of
         :class:`kinto.core.storage.Filter`

     :param int limit: Optionnally limit the number of records to be
        retrieved.

[glasserc]

Optionally 🐑

[gabisurita]

I've just noticed that there is no Total-Records header. I think we should also add it on DELETE for consistency.

[leplatrem]

@gabisurita so it should return the total records that will deleted accross all pages right?

[gabisurita]

@leplatrem Yes, I think so. It should return the number of buckets that would be deleted without pagination.

[leplatrem]

could you open an issue please :) ?
I think it's trivial because we do a get_all() just before performing the deletion...