Restrict Triggered Diagnosis Execution to the Target Device Only

Today, when a triggered diagnosis is initiated through an API-driven trigger to generate a map for an incident, the diagnosis executes against all devices present on the resulting map rather than being limited to the specific device under investigation. This enhancement would scope triggered diagnosis execution so it runs only against the intended target device identified by the incident trigger, regardless of how many other devices appear on the generated map. Limiting execution to the relevant device would reduce unnecessary diagnostic load on unrelated devices and help ensure that diagnostic results remain focused and accurate for the reported issue.