Materialized view modification query adds fields, inner table structure needs to be added

Materialized view modification query adds fields, inner table structure needs to be added
```

CREATE TABLE src_table (`a` UInt32, `b` UInt32) ENGINE = MergeTree ORDER BY a;
CREATE MATERIALIZED VIEW mv (`a` UInt32) ENGINE = MergeTree ORDER BY a AS SELECT a FROM src_table;
INSERT INTO src_table (a, b) VALUES (1, 1), (2, 2);
SELECT * FROM mv;

┌─a─┐
│ 1 │
│ 2 │
└───┘

SET allow_experimental_alter_materialized_view_structure = 1;
ALTER TABLE mv MODIFY QUERY SELECT a, b FROM src_table;
INSERT INTO src_table (a, b) VALUES (3, 3), (4, 4);
SELECT * FROM mv
┌─a─┐
│ 1 │
│ 2 │
└───┘
┌─a─┐
│ 3 │
│ 4 │
└───┘
```

> A clear and concise description of what is the intended usage scenario is.

**Describe the solution you'd like**

In the simple case, if Query adds a field, it checks whether the field in the inner table exists
In the complex case, if Query adds a field, it adds a field in the corresponding inner table