Support Port Variables as Inputs to Path Action Node in Runbooks

The Path action node in Runbook automation currently accepts only source and destination as template variables, with no option to pass source port or destination port as inputs. This enhancement would extend the Path action node to accept source port and destination port as additional template variable inputs, alongside source and destination. Supporting full four-tuple input would allow automated, ticket-triggered path analysis to reflect the exact traffic flow being investigated, improving accuracy for customers running runbook-based triggered automation.