Log disruptive commands / major nemesis steps in db nodes logs

[soyacz]

In db logs we mark start and stop nemesis.
Would be useful to also mark disruption commands that happen on specific node as close as possible to actual disruption trigger. Things like:

1. trigger stop/reboot node
2. trigger decommission abort
3. start reaching enospc
4. abort repair
5. disrupt_memory_stress
6. stop compactions from CompactionOps

refs: #10018 (comment)