GraphQL query merger may get confused with "sort"

[kinow]

Describe the bug

I had two components with similar queries, and it was up to the query merger to combine the queries. While staring at the component and looking for CSS issues, I spotted the cycle points out-of-order (bug found some time ago by @hjoliver, fixed in the GraphQL query with the help of @dwsutherland).

The original query in the Tree view had: taskProxies(sort: { keys: ["cyclePoint"] }) {, while the new component GScan was using a query that had simply taskProxies {. It resulted in the final version missing the sort attribute.

Not sure whether it should be smart to always augment the list of attributes, or warn the user on discrepancies.

Release version(s) and/or repository branch(es) affected?

master

Steps to reproduce the bug

Add a second view, register to the LiveWorkflowService and use a GraphQL attribute without the sort. Then navigate to the Tree component, or use the GScan when/if merged.

Expected behavior

Ordered cycle points as returned by the GraphQL query.

Screenshots

Additional context

Pull requests welcome!
This is an Open Source project - please consider contributing a bug fix
yourself (please read CONTRIBUTING.md before starting any work though).