Elasticsearch scroll deletion fails when scroll IDs are large

[alexvigdor]

ElasticSearch, at least as run in AWS, will sometimes return very large scroll IDs that cause a 413 response on the request to DELETE the scroll used for dateRange queries, since the scroll ID is in the URL. We need to move the scroll ID to the body of the delete request, which will require working around limitations in the apache http client.