Add level merge to "merge" command

[zhanglingzhe0820]

Currently, the cli merge can just execute unseq compaction, it is not conveniently for user to execute compaction. So in this PR, I change the merge command to execute both level compaction and unseq merge. And also, this PR may fix the 'file not found' ci problem.
There is a windows ci problem now.

Every time this ci problem occurs, there will be a file not found error and it is all windows ci. Although the wrong test was not manually merged, I guessed that it was because the last test reported 'file not found' error affected this test
So I speculate that it is caused by an unseq compaction problem.

This error happens because we submit an unseq compaction task manually when a level compaction is working, the unseq compaction will get the current tsfile list and wait for the level compaction to be finished. However, the level compaction may merge the file which will be used in the unseq compaction process. The unseq compaction then cannot find the file to use. Then cause the ci problem.
So in this pr, we change the function of merge cli from the execution of unseq compaction to the execution of level compaction+unseq compaction. It just starts a normal compaction process which do not have this file-related problem.

[jt2594838]

How you intend to solve the problem is a bit out of my expectation. Removing current locks may introduce other issues potentially.
I think the problem is actually one merge does not know that another merge is compacting its chosen files. Can we avoid this from the beginning somehow? For example, a merging mark for those files which are already chosen.

[jixuan1989]

However, the level compaction may merge the file which will be used in the unseq compaction process. The unseq compaction then cannot find the file to use. Then cause the ci problem.

Why it affects query?

[zhanglingzhe0820]

However, the level compaction may merge the file which will be used in the unseq compaction process. The unseq compaction then cannot find the file to use. Then cause the ci problem.

Why it affects query?

Every time this ci problem occurs, there will be a file not found error and it is all windows ci. Although the wrong test was not manually merged, I guessed that it was because the last test reported 'file not found' error affected this test
So I speculate that it is caused by an unseq compaction problem.
And Why it affects query?
When compaction meets error, it may destroy the current tearDown() process and leave some file that not be deleted. The data of these remaining files conflicts with the data inserted in the next test, resulting in query errors

[sonarqubecloud]

SonarCloud Quality Gate failed.

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

77.8% Coverage
0.0% Duplication