[SWDEV-523794] Update to fix MIN_CLK and MAX_CLK incorrect values

(#280)

- Fixed potential issue with min/max values when only one frequency is available
- Improve error handling in GPU frequency range detection
- Refactor clock frequency range detection for better readability
- Added special handling for current frequency indicator (*) in DPM output
- Added comments explaining special case handling for current frequency
- Cleaned up incorrect definitions in hsmp metric table definition

---------

Signed-off-by: Juan Castillo <juan.castillo@amd.com>
Signed-off-by: Maisam Arif <Maisam.Arif@amd.com>
Co-authored-by: Maisam Arif <Maisam.Arif@amd.com>

[ROCm/amdsmi commit: 4d92dea079]

projects/amdsmi/py-interface/amdsmi_interface.py

@@ -1675,8 +1675,7 @@ def amdsmi_get_hsmp_metrics_table(
         "mtbl_socket_thm_residency_acc": mtbl.socket_thm_residency_acc,
         "mtbl_vr_thm_residency_acc": mtbl.vr_thm_residency_acc,
         "mtbl_hbm_thm_residency_acc": mtbl.hbm_thm_residency_acc,
-        "mtbl_gfx_clk_below_host_residency_acc": mtbl.gfx_clk_below_host_residency_acc,
-        "mtbl_low_utilization_residency_acc": mtbl.low_utilization_residency_acc
+        "mtbl_gfxclk_frequency": f"{[round(x*fraction_uq10 ,3) for x in list(mtbl.gfxclk_frequency)]} MHz"
     }
 
 def amdsmi_first_online_core_on_cpu_socket(