[bug](cloud restore) forbid restoring table with property 'light_schema change' = 'false' in cloud mode

[xy720]

What problem does this PR solve?

Avoid restore non-light-schema-change table in cloud mode. Because non-light-schema-change table may have different schema with same schema version(which is always 0), which will cause very bad problem to metadata in cloud mode.

For example:

There is a partitioned table with 'light_schema change' = 'false', its tablet schema is

Tablet a1's schema in Partition A before schema change

schema version 0
col1 uid=0
col2 uid=1
col3 uid=2
col4 uid=3
__delete_sign_column__ uid=4

Now we add column to this table, then:

Tablet a1's schema in Partition A after schema change

schema version 0
col1 uid=0
col2 uid=1
col3 uid=2
col4 uid=3
__delete_sign_column__ uid=4
col5 uid=5

Now we add partition B to this table, then

Tablet b1's schema in Partition B is:

schema version 0
col1 uid=0
col2 uid=1
col3 uid=2
col4 uid=3
col5 uid=4
__delete_sign_column__ uid=5

Then we will have two different tablet schema (a1 and b1) with same index id and same schema version 0 in this table.

This should not happen in cloud mode.

if we backup and restore this table to cluster in cloud mode, the restored table will not be select correctly.

Release note

None

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[xy720]

run buildall

[xy720]

run buildall

[lide-reed]

LGTM

[xy720]

run buildall