Sfc classifier does not work for a reverse path when different egress/ingress port pairs

SFC classifier binds on the SF egress interface of the last RSP hop to be able to properly route the traffic to its original destination in case it is on the same compute as the original source of the traffic.

With the introduction of directional data plane locators for symmetric paths in SFC, the ingress and egress interfaces of a SF might be different and the classifier has to take care to bind to the correct one depending on the direction of the path, wether it is the reverse direction or the forward direction of the symmetric path.

Currently the classifier is binding randomly to one interfaces of the SFC, which makes it work sometimes but not always.