`INFORMATION_SCHEMA.CLUSTER_HARDWARE` table couldn't show `pd` mounted disk info correctly after `tiflash` changed mounted disk

## Bug Report

Please answer these questions before submitting your issue. Thanks!

### 1. Minimal reproduce step (Required)
1. tidb operator deploy tidb cluster in k8s
2. change tiflash mounted disk:
2.1 set tiflash replica to 0
2.2 scale in tiflash to 0
2.3 edit tc tiflash storageClassName
2.4 scale out tiflash

### 2. What did you expect to see? (Required)
1. `INFORMATION_SCHEMA.CLUSTER_HARDWARE` can show `pd` disk info correctly, including `/usr/local/bin`, `/var/lib/pd/log` and `/var/lib/pd/data`
2. tidb dashboard can show pd disk info
### 3. What did you see instead (Required)
1. `INFORMATION_SCHEMA.CLUSTER_HARDWARE` can show `pd` disk info including `/usr/local/bin` and `/var/lib/pd/log`, excluding `/var/lib/pd/data`
2. tidb dashboard cannot show pd disk info

### 4. What is your TiDB version? (Required)
Release Version: v6.4.0-alpha
Edition: Community
Git Commit Hash: aff0c3693f11dacd68525423af9d7187a45b9a82
Git Branch: heads/refs/tags/v6.4.0-alpha
UTC Build Time: 2022-10-08 11:08:32
GoVersion: go1.19.1
Race Enabled: false
TiKV Min Version: 6.2.0-alpha
Check Table Before Drop: false
Store: tikv

Start by reproducing the TiFlash mounted-disk change in a TiDB Operator Kubernetes cluster, then query INFORMATION_SCHEMA.CLUSTER_HARDWARE and check TiDB Dashboard. Trace how PD paths such as /usr/local/bin, /var/lib/pd/log, and /var/lib/pd/data are collected and displayed. Done means all three paths appear correctly in both locations.

Written by the indexing model from the issue text.