fix(nemesis): Fix wrong nemesis usage

[pehala]

Nemesis execution is not intuitive and the actual execution mechanism does not execute code inside disrupt method in nemesis classes, it is only used for pattern matching and then the same method is executed with default arguments.
This PR fixes it and as a consequence we will now test more nemesis, so needs to carefully tested.

ManagerBackup nemesis are in COMPLEX_NEMESIS and as such are not executed by Sisyphus, so for them this PR is not critical but it improves them regardless and brings them closer to how nemesis should look like

• Simplifies manager backup nemesis logic
  • Split into two disrupt methods
  • Remove single use methods
• Fix ClusterRollingRestartRandomOrder by adding new disrupt method

Fixes #13039

Testing

• Nemesis runs
  • ClusterRollingRestartRandomOrder

PR pre-checks (self review)

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

[yarongilor]

the manager backup nemesis works fine in performance test in:
scylla-enterprise-perf-manager-native-backup-nemesis.jenkinsfile
It is not used by Sisyphus, no need to modify it.

[pehala]

the manager backup nemesis works fine in performance test in:
scylla-enterprise-perf-manager-native-backup-nemesis.jenkinsfile
It is not used by Sisyphus, no need to modify it.

Why it is not used by Sisyphus? It has class, it is in the yamls, so it should be used

[pehala]

Why it is not used by Sisyphus? It has class, it is in the yamls, so it should be used

Discussed offline:
Yaron is correct, it is in COMPLEX_NEMESIS and as such is not run. This patch brings it closer to running as proper nemesis, more PRs are needed but this is still improvement and a pushes it in a good direction. Followups will enable it so it runs regularly in supported environments

[fruch]

@pehala @yarongilor why this nemesis are not part of Sisyphus ? where is the reason documented ?

[pehala]

@pehala @yarongilor why this nemesis are not part of Sisyphus ? where is the reason documented ?

Due to bucket and object storage requirements that are region specific. It is not documented and I was confused by it as well, I can add documentation in this PR

I also created task to enable them and we will tackle it in followup

[yarongilor]

LGTM, if nemeses tested and passed.

[scylladbbot]

@pehala new branch branch-2026.1 was added, please add backport label if needed

[fruch]

@pehala
would recommend rebasing, and fixing the precommit issues (new labels for nemesis from other PR)

[pehala]

v2:

• Rebased
• Rerun test in the cover letter to verify