Add HighNodeCPUFrequency runbook

[machadovilaca]

What this PR does / why we need it:

jira-ticket: https://issues.redhat.com/browse/CNV-61568

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

Add HighNodeCPUFrequency runbook

[Copilot]

Pull Request Overview

This PR adds a new runbook detailing the diagnosis and mitigation steps for high CPU frequency issues on nodes.

• Introduces a step-by-step guide for identifying affected nodes and CPU metrics.
• Provides actionable troubleshooting commands and mitigation recommendations.