Parse partition key value from partition_id when need to create part in empty partition

[tavplubix]

Changelog category (leave one):

• Bug Fix (user-visible misbehaviour in official stable or prestable release)

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Some GET_PART entry might hang in replication queue if part is lost on all replicas and there are no other parts in the same partition. It's fixed in cases when partition key contains only columns of integer types or Date[Time]. Fixes #31485.

[tavplubix]

Integration tests - test_lost_part/test.py::test_lost_last_part - need to update the test
Performance - a query from flat_dictionary.xml has unexpected duration, cc: @kitaisreal
Stateless tests flaky check (address, actions) - OK
Stress test (thread, actions) - #31958
Stress test (undefined, actions) - Memory limit (total) exceeded
Unit tests (tsan, actions) - Executor.RemoveTasksStress is flaky, cc: @nikitamikhaylov

[novikd]

LGTM, but I didn't understand why do we need changes in MergeTreeData::getPartitionIDFromQuery.

[tavplubix]

LGTM, but I didn't understand why do we need changes in MergeTreeData::getPartitionIDFromQuery.

Changes in getPartitionIDFromQuery are not related to parsing of partition_id and are not really necessary. I just don't like the way it was implemented before, because saving substring of a query into fields_str in ParserPartition is a hack and using Values format to parse partition expression again also looks strange.

[tavplubix]

Integration tests flaky check (asan) — Failed to read test_results.tsv, cc: @alesapin
Functional stateless tests (release, DatabaseReplicated) - 00993_system_parts_race_condition_drop_zookeeper - #29616, I'm trying to fix it
Stateless tests (release, actions) - 00925_zookeeper_empty_replicated_merge_tree_optimize_final_long is flaky - OPTIMIZE cannot be done on this replica because it is not a leader - #32050
Stateless tests flaky check (address, actions) - Test runs too long - OK
Stress test (thread, actions) - Memory limit (total) exceeded
Unit tests (tsan, actions) - Executor.RemoveTasksStress is flaky, already reported