Allow for Logging of Search API queue requests

Problem/Motivation

Sometimes items which would have been expected to be queued do not appear to be. In order to be able to track down such issues, it would be helpful to know which Edit-since and Edit-to timestamps were used, and what other criteria were used in the query.

This might also require a feature request/change to the orange-dam-php library, depending on implementation.

Proposed resolution

The only way to log the complete request would be for the client library to either 1) store the request into a ->lastRequest property which can then be retrieved for logging or 2) Add it to the response object (which would possibly require overriding Guzzle HTTP's Response class).

An alternative implementation would be to not get all the information about the final request but simply log out the query parameters that were used.

Remaining tasks

Decide on approach. If a change is needed to the orange-dam-php library, a feature request and changeset should be logged there. If we decide to simply log the query parameters, then I think all we need is to add a log statement after the request is made.

User interface changes

None.

API changes

None to the orange_dam module. But possibly a new method added to the Endpoint class in the orange-dam-php library.

Data model changes

None.