Internal VPNs must not be considered by InterVpnLink

At InterVpnLink creation, al Routers are scanned to see if there is any static route in any of them whose nextHop points to an InterVpnLink endpoint. When one of those routes are found, it must be checked that the router belongs to the right VPN (the one oppossite to the endpoint/nexthop).

However the code is currently considering the internal VPNs that could possible be attached to the router, and some routes are not being considered by the InterVpnLink since the router is being wrongly found as belonging to the internal VPN, not to the external one that is being configured in the InterVpnLink.