c-s: Tool creates counter1 table when regular workloads are being run

[muzarski]

Ref: scylladb/scylladb#19107 (comment)

Cassandra-stress frontend always creates standard1 and counter1 tables for all workloads (user is exception). At the time of implementing this, I was sure that original c-s does the same - apparently I was wrong.

In general, the tables we should create for each workload:

• write/read - standard1 table
• counter/counter_read - counter1 table
• mixed - both standard1 and counter1 tables. Better idea might be to create the tables that will be used by the commands provided by the user - e.g. when user provides ratio(write=1,read=2), we should not create counter1 table since it won't be used
• user - a table defined in yaml file with table and table_definition parameters