The query model now supports persisting timestamps. The work package collection and single resource do as well. The query resource of the api v3 however does not. In order to be able to persist the timestamps, the query resource needs to be extended

**Acceptance criteria**

* POST /api/v3/queries (create queries) accepts a timestamp parameter in the message body
* PATCH /api/v3/queries/:id (update query) accepts a timestamp parameter in the message body
* POST /api/v3/queries/form and POST /api/v3/queries/:id/form (form for creating and updating queries) accept timestamp parameters in the message body and the embedded schema explains the added parameter
* Begin of the insertionPOSTEnd of the insertion Begin of the deletion GETEnd of the deletion /api/v3/projects/:id/queries/schema and Begin of the insertionPOSTEnd of the insertion Begin of the deletion GETEnd of the deletion /api/v3/queries/schema declare the added paramter
* Begin of the insertion~~GETEnd of the insertion Begin of the deletion GETEnd of the deletion /api/v3/projects/:id/queries/default, /api/v3/queries/default and /api/v3/queries/:id accept the additional url parameter 'timestamps' similar to how it is done for work Begin of the insertionpackages.~~  Seems to already be supported. Double checking required.End of the insertion Begin of the deletion packages.End of the deletion
* API documentation is updated.