Check the status of all the Pump or Drainer nodes will hit 1105 error with enable tls between tidb enabled

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. What did you do?
   If possible, provide a recipe for reproducing the error.

mysql> show variables like "log_bin";
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| log_bin       | ON    |
+---------------+-------+
1 row in set (0.00 sec)

mysql> show pump status;
ERROR 1105 (HY000): context deadline exceeded
mysql> show drainer status;
ERROR 1105 (HY000): context deadline exceeded

binlogctl works fine.

/var/lib/pump-tls # /binlogctl -pd-urls=https://basic-pd:2379 -cmd pumps -ssl-ca ca.crt  -ssl-cert tls.crt  -ssl-key tls.key
[2023/02/28 03:30:18.738 +00:00] [INFO] [nodes.go:53] ["query node"] [type=pump] [node="{NodeID: basic-pump-0:8250, Addr: basic-pump-0.basic-pump:8250, State: online, MaxCommitTS: 439760982051127298, UpdateTime: 2023-02-28 03:30:17 +0000 UTC}"]

/var/lib/pump-tls # /binlogctl -pd-urls=https://basic-pd:2379 -cmd drainers -ssl-ca ca.crt  -ssl-cert tls.crt  -ssl-key tls.key
[2023/02/28 03:30:55.481 +00:00] [INFO] [nodes.go:53] ["query node"] [type=drainer] [node="{NodeID: basic-drainer651-drainer-0:8249, Addr: basic-drainer651-drainer-0.basic-drainer651-drainer:8249, State: paused, MaxCommitTS: 439760873431760901, UpdateTime: 2023-02-28 03:29:53 +0000 UTC}"]

2. What did you expect to see?
   works fine.

3. What did you see instead?

4. Please provide the relate downstream type and version of drainer.
   (run drainer -V in terminal to get drainer's version)

/var/lib/pump-tls # /drainer -V
Release Version: v6.5.1
Git Commit Hash: 589d79bcc4f0e9fa982847192baf6dd3eb3a0f41
Build TS: 2023-02-16 06:11:19
Go Version: go1.19.5
Go OS/Arch: linux/amd64

Reproduce the failure with TLS enabled between TiDB and the binlog components, using show pump status and show drainer status alongside the working binlogctl commands. Compare the status-query paths and TLS configuration for the reported v6.5.1 environment. Done means both SQL status commands return node information without ERROR 1105 or a context deadline exceeded message.