[FLINK-35198][table] Support the execution of refresh materialized table

[xuyangzhong]

What is the purpose of the change

Support the execution of refresh materialized table.

Brief change log

• Add execution in sql gateway
• Add operation in table-api&table-planner
• Add tests

Verifying this change

Some tests are added.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented?

[flinkbot]

CI report:

• d5717f7 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[lsyldliu]

@xuyangzhong Thanks for your contribution, I left some comments.

[xuyangzhong]

Hi, @lsyldliu all comments have been addressed. Can you take a look again?

[lsyldliu]

What about using the following exception msg:
"Currently, manual refreshing materialized table only supports specifying char and string type partition keys. All specific partition keys with unsupported types are:\n\n %s."

[xuyangzhong]

what about "Currently, manually refreshing materialized table only supports specifying char and string type partition keys. All specific partition keys with unsupported types are:\n\n%s."?

[lsyldliu]

I think we can refer to the following logic, util stringifyOption method.

options.entrySet().stream()
                                        .map(
                                                optionEntry ->
                                                        stringifyOption(
                                                                optionEntry.getKey(),
                                                                optionEntry.getValue()))
                                        .sorted()
                                        .collect(Collectors.joining("\n")))

[xuyangzhong]

We don't need to use the util because the var here is Set<String>, not Map