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.
ops.emplace_back(zkutil::makeSetRequest(path_to_set_hardlinked_files, data, -1));
                }
                Coordination::Responses responses;
                auto error = zookeeper->tryMulti(ops, responses);
                if (error == Coordination::Error::ZOK)
                {
                    created = true;
                    break;
                }
                else if (error == Coordination::Error::ZNONODE && mode != zkutil::CreateMode::Persistent)
                {
                    throw Exception(ErrorCodes::NOT_FOUND_NODE, "Cannot create ephemeral zero copy lock {} because part was unlocked from zookeeper", zookeeper_node);
                }
            }
            else
            {
                Coordination::Requests ops;
                if (!path_to_set_hardlinked_files.empty() && !hardlinked_files.empty())
                {
                    std::string data = boost::algorithm::join(hardlinked_files, "\n");
                    
                    
                    
                    ops.emplace_back(zkutil::makeSetRequest(path_to_set_hardlinked_files, data, -1));
                }
                ops.emplace_back(zkutil::makeCreateRequest(zookeeper_node, "", mode));
                Coordination::Responses responses;
                auto error = zookeeper->tryMulti(ops, responses);
                if (error == Coordination::Error::ZOK || error == Coordination::Error::ZNODEEXISTS)