pump/storge: Measure time taken to write to disk, to rotate and fsync

[suzaku]

cherry-pick #773 to release-3.1

---

What problem does this PR solve?

We only measurer the time taken to write a batch of binlogs at the top level.
But we have no other measurementt to help us figure out which step is taking up most of the time.

What is changed and how it works?

Add 3 metrics:

1. Time taken to write a buf
2. Time taken to rotate
3. Time taken to fsync

Check List

Tests

• Unit test

Code changes

Side effects

Related changes

• Need to update the documentation
• Need to update the tidb-ansible repository

[suzaku]

/run-all-tests

[suzaku]

/run-integration-tests

[july2993]

@suzaku you should merge release-3.0 to address the ci, same as another pr.
fix by https://github.com/pingcap/tidb-binlog/pull/787/files#diff-9f5b9d4e03b955e4e502000abc6d7c3fR17 cause it create the db before restarting drainer

[suzaku]

@suzaku you should merge release-3.0 to address the ci, same as another pr.
fix by https://github.com/pingcap/tidb-binlog/pull/787/files#diff-9f5b9d4e03b955e4e502000abc6d7c3fR17 cause it create the db before restarting drainer

Do you mean release-3.1, this is a PR for the release-3.1 branch.

[july2993]

@suzaku you should merge release-3.0 to address the ci, same as another pr.
fix by https://github.com/pingcap/tidb-binlog/pull/787/files#diff-9f5b9d4e03b955e4e502000abc6d7c3fR17 cause it create the db before restarting drainer

Do you mean release-3.1, this is a PR for the release-3.1 branch.

yes

[suzaku]

/run-all-tests

[july2993]

LGMT

[july2993]

@GregoryIan PTAL

[zier-one]

LGTM