For some reasons when we delete a MergeTree Part in atomic way something may go wrong - and leave the `delete_tmp_*` folder or it's part on disk. This may lead to a disk space consumption over time.

It's suggested to delete this folders at least at server start-up. Current solution with `clearOldTemporaryDirectories()` doesn't work because this method is called periodically from a thread without any locks or advisory on folders - it may cause the race conditions.
LOG_DEBUG(log, "Freezing part {} snapshot will be placed at {}", part->name, backup_path);
        auto disk = part->volume->getDisk();
        disk->createDirectories(backup_path);
        String src_part_path = part->getFullRelativePath();
        String backup_part_path = fs::path(backup_path) / relative_data_path / part->relative_path;
        if (auto part_in_memory = asInMemoryPart(part))
        {
            auto flushed_part_path = part_in_memory->getRelativePathForPrefix("tmp_freeze");
            part_in_memory->flushToDisk(relative_data_path, flushed_part_path, metadata_snapshot);
            src_part_path = fs::path(relative_data_path) / flushed_part_path / "";
        }
        localBackup(disk, src_part_path, backup_part_path);
        /
        /
        createAndStoreFreezeMetadata(disk, part, backup_part_path);
        disk->removeFileIfExists(fs::path(backup_part_path) / IMergeTreeDataPart::DELETE_ON_DESTROY_MARKER_FILE_NAME);
        part->is_frozen.store(true, std::memory_order_relaxed);
        result.push_back(PartitionCommandResultInfo{
            .partition_id = part->info.partition_id,
            .part_name = part->name,
            .backup_path = fs::path(disk->getPath()) / backup_path,
            .part_backup_path = fs::path(disk->getPath()) / backup_part_path,
            .backup_name = backup_name,
        });
        ++parts_processed;
    }
    LOG_DEBUG(log, "Freezed {} parts", parts_processed);
    return result;
}
void MergeTreeData::createAndStoreFreezeMetadata(DiskPtr, DataPartPtr, String) const