What problem does this PR solve?

Issue Number: ref #5237

Problem Summary:

What is changed and how it works?

1. Add check: Check files passed in are ordered and not overlapped.

2. Add check: Check files' range is contained by the ingest range (the ingest range is the region's range).

   Reason: The content of a ColumnFileBig can be only stripped by the segment range (at the read time), not any other range. If the ingest range is smaller than the files' range, for example: ingest_range = [0, 100) and file_data_range = [50, 200), [50, 200) will be still ingested, while [0, 100) will be cleared (if clear_data_in_range = true).

   To avoid surprising results later, we simply forbid this case now.

   Note: Although we specified a stripped range to ingestColumnFiles https://github.com/pingcap/tiflash/blob/09e3a9e2413189070740af58430a9c1da7fe9b72/dbms/src/Storages/DeltaMerge/DeltaMergeStore.cpp#LL849 , the stripped range is only used for delete data, instead of stripping the output.

   This check is risky. We need some time for E2E tests to verify whether there are some unintentional edge cases.

   Currently TiKV has similar checks:

   

3. Introduce ingestFiles to the dm test framework, so that we can write related tests easier.

   As a result, test DeltaMergeStoreRWTest/IngestEmptyFileLists is migrated to StoreIngestTest/EmptyFileLists, simplified using new test framework.

4. Add tests to verify check 1 and check 2, based on the test framework above.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

None