[FLINK-38963][table] Altering query should be possible if MATERIALIZED TABLE schema contains non persisted columns

[snuyanzin]

What is the purpose of the change

Right now if there is MATERIALIZED TABLE with non persisted columns an attempt to alter query will fail since there is an old validation. This validation makes sense (at least in order to keep former functionality) for persisted columns. In case of non persisted these columns should be excluded.

Brief change log

MaterializedTableUtils and tests

Verifying this change

extra tests added + existing tests for the same validation which cover lots of persisted columns cases

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? (yes )
• If yes, how is the feature documented? (not applicable)

[flinkbot]

CI report:

• 6afb434 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

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