What problem does this PR solve?

split PR for #18717

Problem Summary:

1. in new partition stats, we need to collect multiple partitions for a table and save results just as one table.
2. we need a util method to decide to treat a table as new-version-stats or old-version-stats

What is changed and how it works?

What's Changed, How it Works:

this PRs has two commits

1. in the first commit, we purely refactor analyze's table as anlayzeTableID{Persist, Collects}

so we can collect multiple partitions p1, p2, p3 and save as one table t1

2. in the second commit, just add a util method

• stmtctx.CanRuntimePrune: one DML can use new-partition when all touched partition has new stats(stats under tbl, or both tbl, phyTblID has no stats)
• CanRuntimePrune*(): one table can be treated as new-partition when all touched partition has new stats(stats under tbl, or both tbl, phyTblID has no stats)

Related changes

• n/a

Check List

Tests

• Unit test
• Integration test

Side effects

• n/a

Release note

• No release note

This change is