Add routers on top.sls to be able to do a command like sudo salt 'router-002' state.apply roles/router

vmx0 is not always releated to the network intranought, so I add entry["interface_name"] = interface_name
in output of get_carp_entries(), so then in carp.rc the prefixe is based on that.

Fix : we need to use context to call the function get_carp_entries on carp.sls
in place of calling this function on the template carp.rc

Changed the source path in carp.sls into : source: salt://roles/router/carp/files/carp.rc

Added some changes :

The flag hello_ipv6_ovh was missing in web-001, because in netbox the ipv6 was in /56 not in /64.

Add some changes : some flags where missing

Add canonical_public_ipv4 for Ysul

Change the files motd for db-a-001 and db-b-001

rename db-B-001 to db-b-001 across the repository

This change touches Wolfplex files. As such, administrative approval is needed from Wolfplex technical contact.

Rename network interfaces on selected machines to standardize the naming convention across all hosts, using intranought and public.

Updated some functions to preserve a consistent and deterministic
display order by using OrderedDict.

Adjusted the ordering of entries (and the content) in nodes.sls to maintain consistency with the generated pillar structure and ensure deterministic output.

I tried pip install salt==3006.8, but it brings the same strange issue : AttributeError: cannot access submodule 'cmdmod' of module 'salt.modules' (most likely due to a circular import)
(same in WindRiver)

Using a separate file like /etc/rc.conf.d/netif/carp keeps the CARP configuration isolated,
avoids modifying the main /etc/rc.conf, and makes the setup cleaner and safer.
It improves maintainability, reduces the risk of conflicts, and ensures a more modular infrastructure design.

I added a test to determine if the function get_carp_entries() will avoid an FHRP group
if it's not the CARP protocol. Also, it is more readable if we place the CARP configuration directly in the forest.yaml.

We need to use OrderedDict from the collections module because the pillar generation script must preserve the order of the information. This ensures that the generated pillar file remains consistent and human-readable. Maintaining a stable order also makes it easier to review changes, compare versions, and debug configurations.