test(longevity): add longevity with rf=1

[juliayakovlev]

This PR is trying to cover customer issue scylladb/scylladb#16759.
This is from the issue description:

After Upgrading Scylla from 5.2.11 via 5.4.0 to 5.4.1, we started observing missing data in Scylla. 
Every once in a while, an INSERT is committed successfully but the inserted values are not visible 
until Scylla is restarted. 
As far as we can tell, version 5.2.11 was not affected while 5.4.1 is. 5.4.0 was not long enough 
in operation to make a reliable statement.

The suspected bug occurs extremely rarely, making it hard for us to reproduce. 
Out of ~800M inserts per day, only a dozen are affected.

The load is run on keyspace with RF 1 SCT test.
We use scylla-bench because its validate data better then in cassandra-stress

Testing

• longevity-1-rf-test-12h - Scylla version 5.4.1
• longevity-1-rf-test-12h - Scylla version 5.4.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 relevent to this change (if needed)

[juliayakovlev]

@fruch As we discussed, I removed the filter out keyspace by replication factor from this PR.
So in the this new longevity expected disrupt_toggle_table_gc_mode failure with error:

ConfigurationException: tombstone_gc option with mode = repair not supported for table with RF one or local replication strategy

https://argus.scylladb.com/test/e6ef2a1c-7267-4566-9954-f49caa755c50/runs?additionalRuns[]=9c2c48ba-045b-4ef3-90c4-268beca319f3

It will be solved in the separate PR

[juliayakovlev]

@fruch this PR is ready for merge. Please, review

[fruch]

LGTM