Fix parallel workers under the lead process in the GUI

[kmoppel-cognite]

Currently they're jumping around annoyingly. Relevant for vers >= 9.6
where parallel query was added

[blogh]

I think the sort has to be done in two steps.
We sort in reverse order for the time and the other metrics but we have to sort in ascending order for the pid.

cf https://docs.python.org/3/howto/sorting.html#sort-stability-and-complex-sorts

[kmoppel-cognite]

@blogh I think you're right...need some custom sort function...but then...why not to do it in SQL still as I proposed in the first patch - currently actually I think there are no alternative view modes for "Running queries" where rows can be re-ordered in the UI ?

[blogh]

@kmoppel-cognite : we can change the sort order while the display is paused. I need to test if it breaks things.

I'll try to look into this next week on the following one.

[blogh]

So ... we don't sort when paused.
I added a sort step before when we have sortkey.duration anyway.
I think the way parallel processes are handled is just broken ... this will have to do for the moment.

Do you tink it' s ok ?

[blogh]

... of course I forgot mypy ... after black ...
I really should code more often than once every 5 months ...
fixing it ...

[dlax]

Fixed/changed a few minor things based on @blogh commit, rebased and squashed.

LGTM as is; the parallel worker issue can be addressed in a separate changeset.

[dlax]

I think the way parallel processes are handled is just broken

Opened #297 to track this.