feat: support customizing column default values for inserting

[jonahgao]

Which issue does this PR close?

This is a continuation of #8146.

Rationale for this change

Currently, we only support NULL as the default value for columns.
This pr will enable users to customize the default value while creating a table.

For example:

DataFusion CLI v33.0.0

❯ create table t(a int, b int default 100);
0 rows in set. Query took 0.004 seconds.

❯ insert into t(a) values(1);
+-------+
| count |
+-------+
| 1     |
+-------+
1 row in set. Query took 0.007 seconds.

❯ select * from t;
+---+-----+
| a | b   |
+---+-----+
| 1 | 100 |
+---+-----+
1 row in set. Query took 0.006 seconds.

What changes are included in this PR?

• Parsing column default values when constructing the CreateMemoryTable plan.
• The default value of a column can be obtained from the TableSource.
• Fill default value if a column value is not specified during inserting.
• Implement it on MemTable for verification.

Are these changes tested?

Yes

Are there any user-facing changes?

Yes.

• New methods for TableSource and TableProvider, but provided default implementations.
• New field column_defaults in the struct CreateMemoryTable.

[comphead]

would be nice to explain in comments what exactly gets returned in the tuple for future readers, like <column name, expr>
I'm even thinking should be that be a map instead of Vec<>

[jonahgao]

A comment has been added for this.

The main reason is that Hashmap has not implemented the Hash trait, which is required by CreateMemoryTable.

[comphead]

Thanks @jonahgao I think we're very close

[comphead]

lgtm thanks @jonahgao for supporting custom default values

[jonahgao]

Thank you for reviewing @comphead ♥️.

[alamb]

Thank you @jonahgao and @comphead for the review!