CPU usage is misreported.

Currently "0 CPU" means "no CPU metric received in the previous ProfileEvents packet". But there can be many ProfileEvents packets and only a few with CPU increment.

That's why the CPU metric shows something weird like:
```
0
0
0
0
0
1234
0
0
0
...
```

This is unbearable, and the CPU metric should be either fixed or removed altogether.
{
    /// Get columns description from variable or (if it was empty) create it from sample.
    auto columns_description_for_query = columns_description.empty() ? ColumnsDescription(sample.getNamesAndTypesList()) : columns_description;
    if (columns_description_for_query.empty())
    {
        throw Exception(ErrorCodes::LOGICAL_ERROR, "Column description is empty and it can't be built from sample from table. Cannot execute query.");
    }
    /// If INSERT data must be sent.
    rsed_query->as<ASTInsertQuery>();
    if (!parsed_insert_query)
        return;
    bool have_data_in_stdin = !is_interactive && !stdin_is_a_tty && !std_in.eof();
    if (need_render_progress && have_data_in_stdin)
    {
        /// Set total_bytes_to_read for current fd.
        FileProgress file_progress(0, std_in.getFileSize());
        progress_indication.updateProgress(Progress(file_progress));
        /// Set callback to be called on file progress.
        progress_indication.setFileProgressCallback(global_context, true);
    }
    /// If data fetched from file (maybe compressed file)
    if (parsed_insert_query->infile)