[fix](merge-on-write) fix duplicate key in schema change

[liaoxin01]

Proposed changes

During the schema change, the load of new tables did not calculate the delete bitmap, which will be calculated when the schema change is completed. However, due to the lock window issue, the invisible rowset was not calculated at the end of the schema change. So it may result in duplicate keys.

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...

[liaoxin01]

run buildall

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[doris-robot]

TeamCity be ut coverage result:
Function Coverage: 36.41% (8023/22038)
Line Coverage: 28.69% (64445/224640)
Region Coverage: 27.60% (33474/121299)
Branch Coverage: 24.25% (17126/70616)
Coverage Report: http://coverage.selectdb-in.cc/coverage/4e646daf97e2e1d82cb58c733781db771cadd0d6_4e646daf97e2e1d82cb58c733781db771cadd0d6/report/index.html

[doris-robot]

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 45.37 seconds
stream load tsv: 551 seconds loaded 74807831229 Bytes, about 129 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: 28.7 seconds inserted 10000000 Rows, about 348K ops/s
storage size: 17161964870 Bytes

[zhannngchen]

LGTM

[github-actions]

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

[github-actions]

PR approved by anyone and no changes requested.

[xiaokang]

LGTM