add order options to verdi process list

[chrisjsewell]

As it says on the tin! Particularly helpful if you want to list the last x processes, i.e. verdi process list -D desc -l 10

[coveralls]

Coverage increased (+0.01%) to 72.958% when pulling 10d00c0 on chrisjsewell:verdi-proc-list-order into a27811e on aiidateam:develop.

[coveralls]

Coverage increased (+0.006%) to 72.952% when pulling 5f7c933 on chrisjsewell:verdi-proc-list-order into a27811e on aiidateam:develop.

[sphuber]

Great options. Just a small name change request and it would be good if you could at a simple test to aiida.backends.tests.cmdline.commands.process.

[sphuber]

Let's not use an abbreviation here, i.e. let's use --order-direction, especially since the flags are tab completed

[sphuber]

Also name this ORDER_DIRECTION

[sphuber]

Also a question: why do your PR branches always have a commit with message CJS fix, then a shit-ton of Merge remote-tracking branch 'upstream/develop' into develop and then the actual commit with the fix?

[chrisjsewell]

Also a question: why do your PR branches always have a commit with message CJS fix, then a shit-ton of Merge remote-tracking branch 'upstream/develop' into develop and then the actual commit with the fix?

Yeh its because of that that stupid CJS fix commit I made to my develop fork branch. So every time I've updated it, by merging in upstream/devlop, it was adding these extra commits.
I've just run git reset --hard upstream/develop, which looks to have fixed it. However, I've royally screwed up this branch now, so I'm going to close this PR and open a new one with a fresh branch.

[sphuber]

If your fork's develop is messed up, you should do the following:

git checkout develop
git fetch upstream
git reset --hard upstream/develop
git push -f fork develop

The key is to push to your fork again, otherwise you will only just fix it locally.
Also, the best way for PRs in terms of a workflow is to always start from the upstream/develop.
You never really need your fork's `develop.
So always something like:

git fetch upstream
git checkout -b fix_something upstream/develop
git commit # after changes of course
git push fork fix_something

And then make a PR off of that branch.
Then if you need to update, just use rebase instead of merge, i.e.

git fetch upstream
git rebase upstream/develop