topsql, pprof: use hex string but not binary sql/plan digest in goroutine label

[YangKeao]

What problem does this PR solve?

Issue Number: close #52215

Problem Summary:

Use the hex string in goroutine labels. It'll allow us to use the go tool pprof and graphviz to handle the protobuf.

Before this PR returned, you can workaround by generating a dot file, and use iconv to handle the non-utf8 characters manually.

What changed and how does it work?

Use the pre-ecoded hex string, rather than bytes.

Check List

Tests

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

  • I checked and no code files have been changed.

Run any tests (which runs at least some SQLs) and profile it with -cpuprofile, and you'll find the protobuf is useable now.

Release note

None

[codecov]

Codecov Report

Merging #52216 (f12e744) into master (b96f081) will increase coverage by 0.0046%.
Report is 54 commits behind head on master.
The diff coverage is 81.4814%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #52216        +/-   ##
================================================
+ Coverage   70.7107%   70.7154%   +0.0046%     
================================================
  Files          1487       1546        +59     
  Lines        439605     455441     +15836     
================================================
+ Hits         310848     322067     +11219     
- Misses       109287     113411      +4124     
- Partials      19470      19963       +493     

Flag	Coverage Δ
integration	48.9100% <28.0000%> (?)
unit	71.0714% <81.4814%> (+0.5477%)	⬆️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	27.3835% <ø> (-18.4606%)	⬇️

[hawkingrei]

/retest

[YangKeao]

/hold

Wait for @crazycs520's review to confirm it'll not break the TopSQL functionality 🤔. Please unhold it when @crazycs520 thinks it's ready.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-04-01 11:59:10.057597169 +0000 UTC m=+272411.585137707: ☑️ agreed by lance6716.
• 2024-04-01 13:41:21.52315747 +0000 UTC m=+278543.050698015: ☑️ agreed by crazycs520.

[YangKeao]

/unhold

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: crazycs520, hawkingrei, lance6716

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 [crazycs520,hawkingrei,lance6716]

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

[hawkingrei]

/retest

[hawkingrei]

/cherrypick release-7.5
/cherrypick release-7.1
/cherrypick release-6.5

[ti-chi-bot]

@hawkingrei: new pull request created to branch release-6.5: #52322.

In response to this:

/cherrypick release-7.5
/cherrypick release-7.1
/cherrypick release-6.5

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]

@hawkingrei: new pull request created to branch release-7.1: #52323.

In response to this:

/cherrypick release-7.5
/cherrypick release-7.1
/cherrypick release-6.5

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]

@hawkingrei: new pull request created to branch release-7.5: #52324.

In response to this:

/cherrypick release-7.5
/cherrypick release-7.1
/cherrypick release-6.5

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.