Option to restrict QAPP path attribute interface variables to L3 topology interface

When a QAPP consumes a path attribute variable for an interface, such as the inbound interface used to build a command like packet-tracer, the system currently returns both L2 and L3 interfaces for that path node. This produces inaccurate command input and increases QAPP run time when many L2 interfaces are present, since only the single L3 interface displayed on the map is relevant. This enhancement would allow QAPPs to reference the L3 topology interface exclusively when resolving path-based interface variables, matching what is shown on the map. This would improve the accuracy of automated command execution and reduce unnecessary processing time for customers running diagnostic or remediation QAPPs against path attributes.