Improve PowerShell execution and failure backoff for Windows disk metrics collection

[Caideyipi]

Description

• Improve the stability of Windows disk metrics collection when invoking PowerShell.
• Prefer the powershell.exe under SystemRoot / windir to reduce PATH dependency.
• Add a 5-minute retry backoff on failures and throttle repeated failure logs.
• Introduce a PowerShell executor abstraction and add unit tests for both the success path and failure backoff case.

---

This PR has:

• been self-reviewed.
  • concurrent read
  • concurrent write
  • concurrent read and write
• added documentation for new or modified features or behaviors.
• added Javadocs for most classes and all non-trivial methods.
• added or updated version, license, or notice information
• added comments explaining the "why" and the intent of the code wherever would not be obvious
  for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold
  for code coverage.
• added integration tests.
• been tested in a test IoTDB cluster.

---

Key changed/added classes (or packages if there are too many classes) in this PR

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[luoluoyuyu]

Review summary

Improves Windows disk metrics collection: resolves powershell.exe under System32, backs off for 5 minutes after failures, rate-limits failure logs, and injects PowerShellExecutor for testing.

Looks good to merge.

[luoluoyuyu]

During backoff, returning an empty list means disk metrics are temporarily absent rather than stale. Acceptable to stop log storms; optional improvement is to log next retry time at WARN when entering backoff.