[HAL/AMDGPU] Add queue-range counter profiling

Add a separate counter-ranges profiling data family and CLI mode for low-disturbance AMDGPU PMC capture. The existing counters mode remains dispatch-scoped and continues to require retained command-buffer metadata, while counter-ranges avoids dispatch metadata, dispatch event storage, and command-buffer profiling sidecars.

AMDGPU counter sessions now distinguish dispatch samples from queue-carried physical-device ranges. Dispatch sample resources are still enabled on every host queue when requested. Range resources are materialized only on the first host queue for each physical device so device-global PMCs are not started and stopped by overlapping queues. Each range queue owns two pre-created banks, stops the active bank on flush/end, optionally restarts the alternate bank in the same queue-ordered reservation, and writes device-time-range counter samples after the cold flush wait completes.

Range-only profiles now emit begin/end clock correlations so one-shot captures have a real device-clock fit. The Perfetto renderer projects device_time_range counter samples onto separate range-counter tracks, keeping them distinct from dispatch-scoped attribution counters.