During the pruning phase of PCE (when calculating a path), PCE seems to validate all nodes (even those that are used). As a result, sometimes when creating a connectivity service, PCE will define an A/Z endpoints that is in fact already in use and will systematically fail ("No path available by PCE").

The solution of this issue until now was to precise the "device-name" of A/Z endpoints when calling service-create RPC.

To replicate it :

• Create a connectivity service between XPDR-A (xpdr1) and XPDR-C (xpdrc1)
• Create an other connectivity service between XPDR-A (xpdr3) and XPDR-C (xpdrc3)
• The second service creation will fail due to ("No path available by PCE")

Acceptance criteria : the code does not bring regression, associated tests are provided