Method startQuery

src/Interpreters/QueryMetricLog.cpp:162–178

We use TSA_NO_THREAD_SAFETY_ANALYSIS to prevent TSA complaining that we're modifying the query_status fields without locking the mutex. Since we're building it from scratch, there's no harm in not holding it. If we locked it to make TSA happy, TSAN build would falsely complain about `lock-order-inversion (potential deadlock)` which is not a real issue since QueryMetricLogStatus's mutex cannot be l

/// which is not a real issue since QueryMetricLogStatus's mutex cannot be locked by anything else
/// until we add it to the queries map.
void QueryMetricLog::startQuery(const String & query_id, TimePoint start_time, UInt64 interval_milliseconds) TSA_NO_THREAD_SAFETY_ANALYSIS
{
    QueryMetricLogStatus query_status;
    QueryMetricLogStatusInfo & info = query_status.info;
    info.interval_milliseconds = interval_milliseconds;
    info.next_collect_time = start_time;

    auto context = getContext();
    const auto & process_list = context->getProcessList();
    info.task = context->getSchedulePool().createTask(StorageID::createEmpty(), "QueryMetricLog", [this, &process_list, query_id] {
        collectMetric(process_list, query_id);
    });

    UniqueLock global_lock(queries_mutex);
    query_status.scheduleNext(query_id);
    queries.emplace(query_id, std::move(query_status));
}

void QueryMetricLog::finishQuery(const String & query_id, TimePoint finish_time, QueryStatusInfoPtr query_info)
{