[Feature] Statement logger - add to which table statement is executed

[CodeLieutenant]

Problem

Currently statement logger assumes that we have only one table, but gemini has support for multiple tables, and having a statement logger for each table is waste of resources. By not tracking which statement went to which table we don't what whats going on in the statement logger when multiple tables are involved.

Solution

Add a table text column to the partition keys in statement logger, completely remove this limitation. Only the queries have to be adjusted a bit to have this information and each table will be to get it's own schemaChanges partition key so that we know for which table, what DDL statements were executed

[soyacz]

2 questions:

1. if 2 tables have different partition keys, won't we know by this which table was used?
2. how many tests currently use more than one table?

[dani-tweig]

Closing this issue as it was moved to Jira. Please continue the thread in https://scylladb.atlassian.net/browse/QATOOLS-106