[Backport 2024.1] fix(nemesis): make sure set_target_node always set current_disruption

[mergify]

before there was two seprate calls to set_target_node and to set_current_disruption that could end up with set_target_node setting None to the target_node.running_nemesis

this fix move set_current_disruption into set_target_node to avoid this problem, and also introduce a new paramter to set_target_node so any user of it can set what's the data that would be saved on the target node (it's only for debugging)

Fixes: #8198

Testing

• 🟢 https://jenkins.scylladb.com/job/scylla-staging/job/fruch/job/longevity-schema-topology-changes-12h-test/6/

PR pre-checks (self review)

• I added the relevant backport labels
• I didn't leave commented-out/debugging code

Reminders

• Add New configuration option and document them (in sdcm/sct_config.py)
• Add unit tests to cover my changes (under unit-test/ folder)
• Update the Readme/doc folder relevant to this change (if needed)

(cherry picked from commit a12ee91)

Parent PR: #8381

[mergify]

Cherry-pick of a12ee91 has failed:

On branch mergify/bp/branch-2024.1/pr-8381
Your branch is up to date with 'origin/branch-2024.1'.

You are currently cherry-picking commit a12ee91c6.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   sdcm/nemesis.py

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[fruch]

depeneds on #7016