This is an automated cherry-pick of #9530

What problem does this PR solve?

Issue Number: close #9529

Problem Summary:

we get the "suqash delete range" to estimate whether there are sufficient delete rows that we need to compact data in background thread.

In ColumnFileSetSnapshot::getSquashDeleteRange, it use the member variable is_common_handle, rowkey_column_size to generate the rowkey range.
But actually those two variable are not set correctly. is_common_handle is always false in ColumnFileSetSnapshot

So when the table use common-handle, shouldCompactDeltaWithStable always returns false, and the segment background gc is not GC in timely

What is changed and how it works?

Storage: Fix `getSquashDeleteRange` does not return correctly squashed key-range when using common-handle

• Remove unused variable ColumnFileSetSnapshot::{is_common_handle, rowkey_column_size}
• Pass the correct is_common_handle, rowkey_column_size in function shouldCompactDeltaWithStable
• Add check for rowkey-range is_common_handle in DMFilePackFilter

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

Improve the data background GC speed on clustered-index table
提升聚簇索引的表后台回收过期数据的速度