[HAL/AMDGPU] Sample counter ranges on a profile queue

Counter range profiling was hard-coded to host queue 0. That is also the deterministic target for IREE_HAL_QUEUE_AFFINITY_ANY, so a 1ms periodic flush could not interrupt a long submitted workload: the range stop/start packets sat behind the work they were supposed to sample.

Route counter range enable/start/flush through a small queue-selection helper and use the final host queue for range sampling, with queue 0 as the one-queue fallback. This keeps the default queue available for ordinary submissions while letting the profiling flusher run near its requested cadence on devices with multiple host queues.

A 100-iteration SDXL prompt-encoder capture at a 1ms flush interval moved from 204 device-time-range samples with 5.47ms average range duration to 1102 samples with 0.98ms average range duration. Add coverage that device-time-range counter samples are accepted by the test sink and are emitted on the selected profile queue.