Bulk command scroller should be aligned on the underlying page provider

As observed in WEBUI-423, when invoking the Bulk.RunAction operation on a page provider relying on Elasticsearch (e.g. advanced_document_content), the bulk command that is submitted doesn't use an Elasticsearch scroller. This can lead to some wrong results, depending on the query syntax, for instance, filtering the title on "my*" works against Elasticsearch but not MongoDB.

We should align the scroller on the type of page provider: ElasticSearchNxqlPageProvider -> elastic scroller, default otherwise.

We should also apply this mechanism to the "search" endpoint.