Correct L3 topology mapping when duplicate interface names exist on PE devices

NetBrain currently does not validate or account for cases where multiple provider edge devices use interfaces with the same name, which can cause the platform to incorrectly resolve L3 link endpoints and produce an inaccurate topology map. This enhancement would add logic to detect duplicate interface names across devices during L3 topology calculation and either enforce interface name uniqueness or correctly disambiguate links using additional attributes such as IP addressing or device context. Customers managing large multi-vendor or multi-tenant environments would benefit from accurate automated topology mapping without needing to manually identify and correct link errors caused by naming collisions.