fix(server): 🐛 fix issue with Almalinux getting a static IP

Summary

When deploying a range with Almalinux templates the VMs don't get the static IP as defined in the range config. The output (1) represents the unreachable status off VMs. The output (2) represents the VMs with DHCP IP after the step (1).

Steps to reproduce

# Get Almalinux templates
git clone https://github.com/Croko-fr/ludus-templates.git

# Add the templates
cd ludus-templates
ludus template add -d Almalinux/almalinux-8-10-x64-us-server
ludus template add -d Almalinux/almalinux-9-3-x64-us-server

# Build the templates
ludus template build -n Almalinux/almalinux-8-10-x64-us-server-template
ludus template build -n Almalinux/almalinux-9-3-x64-us-server-template

# Define the config in this issue
ludus range config set -f issue_range.yml

# Deploy the range
ludus range deploy

Output

(1) ludus range deploy

PLAY RECAP *********************************************************************
alma8.10                   : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0   
alma9.3                    : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0

(2) ludus range list

|    188     | alma8.10                   |  On   | 10.5.20.157 |
|    189     | alma9.3                    |  On   | 10.5.20.165 |

Range config

ludus:
  - vm_name: "alma8.10"
    hostname: "alma8.10"
    template: almalinux-8-10-x64-us-server-template
    vlan: 20
    ip_last_octet: 8
    ram_gb: 4
    ram_min_gb: 1
    cpus: 1
    linux: true
  - vm_name: "alma9.3"
    hostname: "alma9.3"
    template: almalinux-9-3-x64-us-server-template
    vlan: 20
    ip_last_octet: 9
    ram_gb: 4
    ram_min_gb: 1
    cpus: 1
    linux: true

FIX

Almalinux identified templates don't change to Static IP cause the server doesn't have credentials to connect to the VMs. This FIX adds the attended credentials.