Convert renaming tables

[avibrazil]

Please add CLI option to add prefix or suffix to converted table names.

Something like:

sqlite3mysql … --prefix converted_ --suffix _instrumented ...

So a SQLite source table named my_table will be created on MariaDB as converted_my_table_instrumented

[techouse]

@avibrazil Thanks for the suggestion!

In #158 I've explored what it would take to add a table-name prefix so transfers could land alongside existing MySQL tables without collisions. Unfortunately the scope ended up much larger than it first appeared: every place we reference a table, i.e. CREATE/INSERT statements, foreign keys, indexes, view rewrites, error handling, even the retry logic, would need to run through a new naming mapper. That’s doable, but the blast radius is huge and it’s easy to miss a call-site or introduce regressions around constraints. I’d have to add a lot of new plumbing and tests just to keep things consistent across the entire transporter.

Given that risk profile, the payoff felt limited. If someone wants to inspect or stage the data under a different name, it’s pretty straightforward to create a separate schema (or temporary database) in MySQL, run sqlite3mysql against it, and then use their usual admin tooling to rename or copy tables as needed. That keeps the migration tool simple and avoids adding yet another switch that could subtly break production transfers.

For those reasons I'm going to pass on implementing table prefixes/suffixes.