fix: properly configure IPv6 through Gateway6+IPV6Address

[pborn-ionos]

Issue #, if available:
Fixes #39

Description of changes:

Although the primary change is around having Gateway6 properly set in the cloud-init network configuration, so gateway ::/0 can be set, i figured it might make sense to still separate it a bit more into Gateway6 and IPV6Address, so it's more clear what's referenced with those variables.

Testing performed:

Extensive redeployments and cloud-init config extraction.

DUALSTACK

network:
  version: 2
  renderer: networkd
  ethernets:
    eth0:
      match:
        macaddress: DA:A3:1B:83:BF:A4
      dhcp4: 'no'
      addresses:
        - 192.168.0.61/24
        - 2001:dead:beef:aaaa::a/64
      routes:
        - to: 0.0.0.0/0
          via: 192.168.0.1
        - to: '::/0'
          via: 2001:dead:beef:be24:11ff:fe20:b2ed
      nameservers:
        addresses:
          - 8.8.8.8
          - 8.8.4.4

IPV6-only

network:
  version: 2
  renderer: networkd
  ethernets:
    eth0:
      match:
        macaddress: 3E:87:D2:F9:17:AE
      dhcp4: 'no'
      addresses:
        - 2001:dead:beef:aaaa::a/64
      routes:
        - to: '::/0'
          via: 2001:dead:beef:be24:11ff:fe20:b2ed
      nameservers:
        addresses:
          - 8.8.8.8
          - 8.8.4.4

IPv4-only

network:
  version: 2
  renderer: networkd
  ethernets:
    eth0:
      match:
        macaddress: 26:BB:01:A4:8C:84
      dhcp4: 'no'
      addresses:
        - 192.168.0.61/24
      routes:
        - to: 0.0.0.0/0
          via: 192.168.0.1
      nameservers:
        addresses:
          - 8.8.8.8
          - 8.8.4.4

[mcbenjemaa]

LGTM

[pborn-ionos]

@mcbenjemaa as the PR wasn't ready-to-review when you had a look at it, would you mind giving it the approval ✅, so the auto-merge can run through? :)

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud