improvement(fullscan): Add CQL TIMEOUT parameter to full-scan query
improvement(fullscan): Add CQL TIMEOUT parameter to full-scan query

	A random value for TIMEOUT is added for page fetch (page size = 100k).
	The timeout value is between 2 to 300 seconds.

Testing description:

SCT has a ‘full-scan’ nemesis-like operation that reads an entire table.
An optional ‘timeout’ parameter can be added to this query, that gets a randomized value between several minutes - to several hours.
During the time processing this query TIMEOUT threshold, the DB nodes are having other disruptive nemesis as well.

The idea is to challenge this new cql timeout mechanism and to generally verify there are no unexpected results. that means its queries either succeed or fail for the timeout threshold expected error message. it doesn't validate that the timeout did measure the correct time duration (that is covered in Dtest).

The full scans can last either few minutes or much longer (depend on selected table) so the idea is taking these specific time points to challenge both successful and unsuccessful query to all relevant tables and duration in a balanced probability.

see also full test plan here: https://docs.google.com/document/d/1TF_GmKWwjw3OsS_ZwGIScNUYrWjnWedRpVxzAcL2lqg/edit?usp=sharing

scylladb/scylla-cluster-tests,scylladb/scylla-longevity-tests,scylladb/scylla-cluster-tests,scylladb/scylla-longevity-tests,scylladb/scylla-cluster-tests,scylladb/scylla-cluster-tests,scylladb/scylla-longevity-tests,scylladb/scylla-cluster-tests