Add User Cancel Event to Journal, Server cancel replaced with Abort

[Dym03]

This PR finishes work on #1001 with the addition of JobCancel event into the Journal. Also this PR introduces difference between cancellation of Task made by user and hq, as was suggested by @spirali so canceled tasks are canceled by user and aborted tasks are canceled by the hq.

I would like to hear your opinion if the colors suggested are okay with you

create_dataset(&aborted, "Aborted", Color::LightCyan) and
DashboardTaskState::Aborted => Color::LightCyan
Example below:

Documentation:

I will update the documentation once I get agreement that this state is wanted

Sorry for not dividing it into a smaller chunk, like only the addition of the JobCancel, but while I was at it, I just took a shot at doing it at once :P.

[Dym03]

Updated test so it matches the new aborted state.

[spirali]

LGTM.
Random thoughs:

• Maybe color should be more similar to "Failed" as it something happen from runtime not from a user command.
• We can think about (not in this PR) if not to use Abort also after reaching crash counter (it now sets a Failed state, but technically it is not that the fail of the task itself), but it would be nice to distinguish between "abort-after-dep" and "abort-after-crash".

[Dym03]

Okey, will look at the colorway. And update the documentation. Also there are some minor bugs of Abort, that will be fixed.
About the crash counter, that as you said could be changed in another PR.

[Dym03]

Actually finding all the places that this would affect took me a while. But god bless tests, that forced me to do it. Hopefully I have managed to discover all the places.

Example of the colorway in dashboard:

[spirali]

I like the final colors.

I have just put one change request to the documentation; otherwise it is ready to merge.

[spirali]

Change just to:

Waiting--------------------\
   | ^                     |
   | |                     |
   v |                     |
Running--------------------|
   | |                     |
   | \--------\            |
   |          |            |
   v          v            v
Finished    Failed   Canceled/Aborted

[Dym03]

Documentation updated, I think with this merged the #1001 can be closed. And maybe new Issue can be opened to capture the thought about the distuguish of the Abort due to Dependency/ Abort due to crash of worker | due to max fails. I have found 2 more things that needs an update, so I will update them later today.

[Dym03]

Updated documentation about the addition of the Aborted state also in the Job, to keep the original idea of propagating the task state to the Job state. But it is also mentioned in the documentation that this shouldn't happen as aborted state is closely connected to the failure of the task, which would imply that this Job State shouldn't be reached, in the current state.
But I think that it should be added, as if there ever in the future there could be abortion of the task without the need of a failure of a task, I think this should be ready to go :).