[DataQuery] New DQT backend implementation

[driusan]

This is intended to make it easier to review/test #8219 or #8216 by implementing the swagger schema, so that it can be tested via the the api docs module.

It's blocked by #8221 and #8260. In order to have anything to query against, you probably also need #8216 (or another QueryEngine implementation for a module.)

Nonetheless, the implementation should be complete (other than the one endpoint described as aspirational in the swagger schema.) and can be reviewed. I may have broken something while trying to extract it from the branch where I was developing the frontend or while trying to appease phpcs/phan.

[driusan]

Needs work, not in sync with the latest updates to #8219

[xlecours]

I have sent the proposed data to POST /dataquery/queries and got a 200 {"QueryID": 1}
But then, using GET /dataquery/queries nothing shows

[driusan]

I believe the sample data in the schema.yml assumes that the candidate_parameter's QueryEngine is implemented (Done in PR#8288, as of now unmerged). It should have returned a 400 error. It looks like it accepted it because of this FIXME needing to be implemented: https://github.com/aces/Loris/pull/8268/files#diff-d21396483bc372130220b07b323e521f63ff1aca56372eb09102c3b4c19e324aR65

[xlecours]

This makes sense. It's hard to test until there is a frontend to it.

[driusan]

TODO: After this PR is merged make an issue about instruments module needing to separate viewing data permission from data_entry. (Currently, the instruments module does has a hasPermission('data_entry') permission check. That means that you need data_entry to query the module data in the dataquery module.)

[zaliqarosli]

Looks good! the only issue I had is the one already added by dave as a to-do above ^^

[driusan]

@zaliqarosli @xlecours re-factored code as per Xavier's request, can you guys re-review?

[xlecours]

Let's roll :)