[enhancement](schema) Add schema consistency check when add partition

[luwei16]

Proposed changes

Issue Number: close #xxx

When adding partition, add schema consistency check to reduce the possibility of inconsistency between FE and BE schema.

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

[dataroaring]

run buildall

[luwei16]

run buildall

[doris-robot]

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.64 seconds
stream load tsv: 595 seconds loaded 74807831229 Bytes, about 119 MB/s
stream load json: 20 seconds loaded 2358488459 Bytes, about 112 MB/s
stream load orc: 64 seconds loaded 1101869774 Bytes, about 16 MB/s
stream load parquet: 31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select: 29.0 seconds inserted 10000000 Rows, about 344K ops/s
storage size: 17162184138 Bytes

[morningman]

Can it be covered by case?

[dataroaring]

LGTM

[github-actions]

PR approved by at least one committer and no changes requested.

[github-actions]

PR approved by anyone and no changes requested.

[luwei16]

Can it be covered by case?

Existing regression cases can partially cover it, but the code with meta_changed = true cannot be covered because this is an abnormal scenario.