INSERT statements without target column list are not working

[gruuya]

Describe the bug
Planning of INSERT statements does not allow for omitting target column list in the SQL statement.

To Reproduce

❯ create table test as values (1, 2);
0 rows in set. Query took 0.149 seconds.
❯ insert into test values (3, 4);
Plan("Column count doesn't match insert query!")
❯ insert into test(column1, column2) values (3, 4);
Internal("Unsupported logical plan: Dml")

The first error should be the same as the second, which comes from the stubbed out physical planning implementation.

Expected behavior
It is generally accepted that the target column list is optional, and if omitted the target is assumed to be all the columns in the schema.

Additional context
Related to the new LogicalPlan::Dml node for WriteOp::Insert (handled in insert_to_plan).