User Story: As a network administrator, I want to configure routes in OpenShift installations using a MAC address as an identifier so that I can specify routes without needing to know the interface name during image-based installations.   Acceptance criteria: Given a system administrator setting up an OpenShift environment with image-based installation and preparing a YAML configuration for network interfaces with MAC addresses specified and the identifier set to `mac-address`, When they submit a route configuration where the `next-hop-interface` is specified using a profile-name or directly using a MAC address that matches an earlier specified interface,   Then, Nmstate should match the `next-hop-interface` based on the MAC address or profile name from the corresponding interface section and the route configuration should apply without requiring the explicit name of the network interface. Definition of Done: The implementation meets the acceptance criteria Integration tests are written and pass The new feature is part of a downstream build attached to an errata This new feature is documented in RHEL and the nmstate.io official documentation is also updated.

.Nmstate now supports configuring routes by using a MAC address instead of an interface name With Nmstate, you can create a network connection by assigning it to the MAC address of an interface. With this enhancement, you can use the profile name instead of the interface name in the `next-hop-interface` parameter in the routing configuration. With this feature, you can create static routes without knowing the interface name.