Implement distance functionality from fcm

[Honigeintopf]

The FCM is able to define a distance to the firewalls it creates.
The firewall controller isn't able to do that yet, which this issue aims to improve.

[Honigeintopf]

Right now, firewalls are chosen randomly to send network requests. This random selection sometimes causes one firewall to send a request, but a different firewall to receive the response. This mismatch causes dropped packets and breaks network communication.

What Needs to Be Done

1. Get the Distance: The firewall controller already retrieves a distance setting from the Firewall CRDs (custom resources). This distance setting is already in place and does not need to be changed.
2. Update Routing Paths: Inside the metal-networker code, there is a function to update routing paths in the FRR (Free Range Routing) configuration. This function needs to use the distance setting from the firewall controller to adjust the routing paths so that requests and responses go through the same firewall.

Solution Summary

1. Use the distance value to extend routing paths in the FRR configuration.
2. This will make sure that the same firewall handles both the request and response, preventing packet drops and improving network stability.

[Honigeintopf]

AS path prepend