Query operation name in logs randomly chooses between detail.operation.query.operationName and detail.query.operationName

### Version Information

Server Version:
2.0.9
### Environment

Docker swarm

### What is the expected behaviour?

Hasura query log json should have a single field operationName that says what the operation name of the query was. Is there a reason both of these keys in the json blob exist? it seems redundant

### Keywords

operationName
incorrect logs

### What is the current behaviour?

the operation name is randomly put between either
detail.operation.query.operationName or detail.query.operationName but never both

### How to reproduce the issue?

* read logs in column form with the two json keys
* notice that only one key is ever populated
### Screenshots or Screencast
Query names are censored but you can clearly see the behavior I mentioned above with it flip/flopping.
At a glance when looking through the logs it appears that each query type chooses one or the other consistently

Start by reproducing the issue from Docker Swarm logs and compare the two reported operationName paths across query types. The change is done when each query log exposes one consistent operationName field without the flip-flopping described in the report.

Written by the indexing model from the issue text.