What problem does this PR solve?

Issue Number: close #55819

Problem Summary:
During TRUNCATE PARTITION writes was blocked to partitions that was being truncated, also during StateDeleteReorganization, meaning the DDL would block writes to all truncated partitions for the full duration of the DDL, in case of a Global Index.

What changed and how does it work?

Instead of simply blocking writes to partitions being truncated, we are hiding the new partitions from Global Indexes StateWriteOnly and old partitions from StateDeleteOnly so that they cannot be seen, and not cause any anomaly, where you can find data or not depending on access method, i.e. it may be found if using Global Index, but not for table scan.

A side effect of this is that we are still blocking duplicate keys, if a write to a global unique index from a StateDeleteOnly client that collides with a not-yet cleaned up Global Index entry, or a write to a global unique index from StateWriteOnly (old partition, to be truncated) collides with a newly written entry in StateDeleteOnly (using the new emptied partition).

To not generate these kind of duplicate errors for too long period, duplicate key errors are not generated during StateDeleteReorganization if the duplicate comes from an old truncated partition, instead that global unique index entry is overwritten.

Also refactored/deduplicated code for cleaning up the global index entries from dropped/truncated partitions, so both DROP and TRUNCATE PARTITION uses the same code.

Check List

Tests

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

  • I checked and no code files have been changed.

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

Please refer to Release Notes Language Style Guide to write a quality release note.

Removed write blocking partitions involved in TRUNCATE PARTITIONs if they had a Global Index.