Swagger schema doesn't include max-query-timeout

[Robsteranium]

This in turn means that the Martian client won't add this to the request - it's ignored if if you pass it as a keyword argument (to e.g. post-query-live).

We could do with permitting the OOK etl pipeline to run with a longer timeout because truncation of results can go undetected.

The only way to do this at the moment is with the JWS-signed max-query-timeout parameter. Ultimately we ought to rework the timeout authorisation to use auth0 with some sort of drafter:privileged permission #357.

In the meantime it'd be good to at least extend the swagger schema to support the legacy behaviour.