Alter the restore nemesis for raft (and tablets) scenarios

[xtrey]

It's a regression. This is a reopening for #7318
It was fixed in #8342 and backported to 6.1 here #8579 on 6 of September. However, this run has exactly the same issue:

File "/home/ubuntu/scylla-cluster-tests/sdcm/mgmt/cli.py", line 1140, in run
raise ScyllaManagerError(f"Encountered an error on sctool command: {cmd}: {ex}") from ex
sdcm.mgmt.common.ScyllaManagerError: Encountered an error on sctool command: restore -c cd03b6f1-4be2-457d-aede-5f75ad1bca1f --restore-schema --location s3:manager-backup-tests-permanent-snapshots-us-east-1  --snapshot-tag sm_20240812150350UTC: Encountered a bad command exit code!
Command: 'sudo sctool restore -c cd03b6f1-4be2-457d-aede-5f75ad1bca1f --restore-schema --location s3:manager-backup-tests-permanent-snapshots-us-east-1  --snapshot-tag sm_20240812150350UTC'
Exit code: 1
Stdout:
Stderr:
Error: create restore target, units and views: init target: restore into cluster with given ScyllaDB version and consistent_cluster_management is not supported. See https://manager.docs.scylladb.com/stable/restore/restore-schema.html for a workaround.
Trace ID: 8100_xqcRgS-9zWF7-CNmw (grep in scylla-manager logs)