*: refine tikv/client-go log to print context information(such as conn id) as much as possible

[crazycs520]

What problem does this PR solve?

Issue Number: close #45558

Problem Summary: refine tikv/client-go log to print context information(such as conn id) as much as possible.

What is changed and how it works?

Use Logger(ctx) instead of BgLogger as much as possible.

Since Logger(ctx) maybe contain other information such as connection id, which is good for debug.

Here are some log before this PR:

[2023/07/25 16:02:19.812 +08:00] [WARN] [region_request.go:612] ["unable to find stores with given labels"] [labels="[{\"key\":\"zone\",\"value\":\"z99\"}]"]
[2023/07/25 16:01:34.877 +08:00] [WARN] [region_request.go:1942] ["tikv reports `DataIsNotReady` retry later"] [store-id=4] [peer-id=8008] [region-id=1011] [safe-ts=443094687287869442] [ctx="region ID: 1011, meta: id:1011 start_key:\"t\\200\\000\\000\\000\\000\\000\\000`_r\\00100000000\\37700000000\\37700000000\\377051486\\000\\000\\375\\0010000-000\\3771\\000\\000\\000\\000\\000\\000\\000\\370\\003\\227s\\332eMU\\256\\350\" end_key:\"x\\000\\000\\000\" region_epoch:<conf_ver:77 version:63 > peers:<id:8006 store_id:1 > peers:<id:8007 store_id:14 > peers:<id:8008 store_id:4 > , peer: id:8008 store_id:4 , addr: 10.0.1.9:22160, idx: 0, reqStoreType: TiKvOnly, runStoreType: tikv"]
[2023/07/25 16:05:33.038 +08:00] [WARN] [backoff.go:158] ["regionMiss backoffer.maxSleep 40000ms is exceeded, errors:\nepoch_not_match:<>  at 2023-07-25T16:05:30.479434+08:00\nsend tikv request error: no available connections, ctx: region ID: 7034, meta: id:7034 start_key:\"r\\000\\000\\001\" end_key:\"t\\200\\000\\000\\000\\000\\000\\000`_r\\00100000000\\37700000000\\37700000000\\377051486\\000\\000\\375\\0010000-000\\3771\\000\\000\\000\\000\\000\\000\\000\\370\\003\\227s\\332eMU\\256\\350\" region_epoch:<conf_ver:59 version:63 > peers:<id:7035 store_id:7 > peers:<id:7036 store_id:3 > peers:<id:8002 store_id:2 > , peer: id:7036 store_id:3 , addr: 10.0.1.9:21161, idx: 0, reqStoreType: TiKvOnly, runStoreType: tikv, try next peer later at 2023-07-25T16:05:30.99473+08:00\nepoch_not_match:<>  at 2023-07-25T16:05:32.538+08:00\nlongest sleep type: tikvRPC, time: 23808ms"]

In this PR, those logs will contain conn information:

[2023/07/31 14:41:16.401 +08:00] [WARN] [region_request.go:615] ["unable to find stores with given labels"] [conn=1822425092] [region=31] [leader-invalid=false] [labels="[{\"key\":\"zone\",\"value\":\"z99\"}]"]
[2023/07/31 14:41:16.404 +08:00] [WARN] [region_request.go:2018] ["tikv reports `DataIsNotReady` retry later"] [conn=1822425092] [store-id=12] [peer-id=164] [region-id=31] [safe-ts=443229319455309828] [ctx="region ID: 31, meta: id:31 start_key:\"t\\200\\000\\000\\000\\000\\000\\000`\" end_key:\"t\\200\\000\\377\\377\\377\\377\\377\\371\" region_epoch:<conf_ver:5 version:58 > peers:<id:32 store_id:5 > peers:<id:112 store_id:1 > peers:<id:164 store_id:12 > , peer: id:164 store_id:12 , addr: 10.0.1.9:20161, idx: 0, reqStoreType: TiKvOnly, runStoreType: tikv"]
[2023/07/31 14:42:58.334 +08:00] [WARN] [backoff.go:172] ["regionMiss backoffer.maxSleep 40000ms is exceeded, errors:\nsend tikv request error: no available connections, ctx: region ID: 31, meta: id:31 start_key:\"t\\200\\000\\000\\000\\000\\000\\000`\" end_key:\"t\\200\\000\\377\\377\\377\\377\\377\\371\" region_epoch:<conf_ver:5 version:58 > peers:<id:32 store_id:5 > peers:<id:112 store_id:1 > peers:<id:164 store_id:12 > , peer: id:164 store_id:12 , addr: 10.0.1.9:20161, idx: 0, reqStoreType: TiKvOnly, runStoreType: tikv, try next peer later at 2023-07-31T14:42:53.995741+08:00\nregion_id:31, region_ver:58, store_type:tikv, peer_addr:10.0.1.9:20161, error:epoch_not_match:<>  at 2023-07-31T14:42:55.923103+08:00\nsend tikv request error: no available connections, ctx: region ID: 31, meta: id:31 start_key:\"t\\200\\000\\000\\000\\000\\000\\000`\" end_key:\"t\\200\\000\\377\\377\\377\\377\\377\\371\" region_epoch:<conf_ver:5 version:58 > peers:<id:32 store_id:5 > peers:<id:112 store_id:1 > peers:<id:164 store_id:12 > , peer: id:164 store_id:12 , addr: 10.0.1.9:20161, idx: 0, reqStoreType: TiKvOnly, runStoreType: tikv, try next peer later at 2023-07-31T14:42:56.425557+08:00\ntotal-backoff-times: 46, backoff-detail: regionMiss:23, tikvRPC:23\nlongest sleep type: tikvRPC, time: 32815ms"] [conn=1822425092]

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @crazycs520. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-08-01 02:51:35.657761854 +0000 UTC m=+153779.600110377: ☑️ agreed by ekexium.
• 2023-08-01 03:11:41.017832966 +0000 UTC m=+154984.960181497: ☑️ agreed by hawkingrei.

[cfzjywxk]

/merge

[ti-chi-bot]

@cfzjywxk: We have migrated to builtin LGTM and approve plugins for reviewing.

Please use /approve when you want approve this pull request.

The changes announcement: LGTM plugin changes

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfzjywxk, ekexium, hawkingrei, MyonKeminta, you06

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [MyonKeminta,cfzjywxk,ekexium,hawkingrei,you06]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

Merging #45559 (92def41) into master (0e068ed) will increase coverage by 0.1838%.
Report is 3 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #45559        +/-   ##
================================================
+ Coverage   73.2002%   73.3840%   +0.1838%     
================================================
  Files          1265       1268         +3     
  Lines        390134     391818      +1684     
================================================
+ Hits         285579     287532      +1953     
+ Misses        86238      86002       -236     
+ Partials      18317      18284        -33     

Flag	Coverage Δ
integration	78.1388% <ø> (?)
unit	73.3758% <100.0000%> (+0.1756%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	54.0444% <ø> (ø)
parser	85.0467% <ø> (+0.0108%)	⬆️
br	52.0368% <ø> (+0.0461%)	⬆️

[hawkingrei]

/retest

[crazycs520]

/test unit-test

[tiprow]

@crazycs520: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test unit-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[crazycs520]

/ok-to-test