API query params presets

[etj]

Short description

We want to define presets to be included in the API queries, that will be expanded server side in multiple query params.

Rationale

After implementing the fixes in #12079, it is now possible to request a specific set of fields, so that DB queries and data retrieval are optimized.

The GeoNode/MapStore client anyway performs some fixed requests, with a limited number of fields, but big enough t make the request URL cumbersome.

Proposed solution

In settings we can add the presets, for instance:

REST_API_PRESETS = {
"q1": {"exclude[]":"*", "include[]": ["pk", "title", "data"]},
"linked": {"exclude[]":"*", "include[]": ["pk", "linked_resources"]}
}

The requesting URL may be something like:
http://server/api/v2/resources?api_preset=q1

There will be a new Filter that modifies the request parameters, replacing the preset request with the related content; so the previous request will be the equivalent of:
http://server/api/v2/resources?exclude[]=*&include[]=pk&include[]=title&include[]=data

Pls note that the query params will be merged, so a request like
http://server/api/v2/resources?api_preset=q1&include[]=perms
will be transformed into
http://server/api/v2/resources?exclude[]=*&include[]=pk&include[]=title&include[]=data&include[]=perms

Caveats

The filter will only expand a preset wherever it is declared. It does not know whether the called entrypoint will really deal with the parameters, so it will be up to the client to make sure the preset will really work with the requested operation.