Question about string to utf8view when creating table

```sql
> CREATE TABLE t1 AS VALUES
('2021', 3, 'A'),
('2022', 4, 'B'),
('2023', 5, 'C');
0 row(s) fetched.
Elapsed 0.014 seconds.

> describe t1;
+-------------+-----------+-------------+
| column_name | data_type | is_nullable |
+-------------+-----------+-------------+
| column1 | Utf8 | YES |
| column2 | Int64 | YES |
| column3 | Utf8 | YES |
+-------------+-----------+-------------+
```

Should we also map the column1 and column3 to utf8view if `map_string_types_to_utf8view` is true?

If so, I'll open a PR to fix

Start by reproducing the CREATE TABLE AS VALUES and DESCRIBE example in the issue with map_string_types_to_utf8view enabled. Trace the handling of string columns during table creation and check the existing tests for this option; done means the resulting string columns consistently use the intended UTF-8 view type.

Written by the indexing model from the issue text.