staging: Add clearly-defined node

Related to T2865

Test Plan

terraform plan happy:

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # module.clearly-defined.proxmox_vm_qemu.node will be created
  + resource "proxmox_vm_qemu" "node" {
      + agent        = 0
      + balloon      = 1024
      + bios         = "seabios"
      + boot         = "c"
      + ciuser       = "root"
      + clone        = "debian-buster-2020-11-06"
      + clone_wait   = 15
      + cores        = 2
      + cpu          = "host"
      + desc         = "Node to host development for clearly defined"
      + force_create = false
      + full_clone   = false
      + hotplug      = "network,disk,usb"
      + id           = (known after apply)
      + ipconfig0    = "ip=192.168.130.200/24,gw=192.168.130.1"
      + kvm          = true
      + memory       = 8192
      + name         = "clearly-defined"
      + nameserver   = "192.168.100.29"
      + numa         = false
      + onboot       = true
      + os_type      = "cloud-init"
      + preprovision = true
      + searchdomain = "internal.staging.swh.network"
      + sockets      = 1
      + ssh_host     = (known after apply)
      + ssh_port     = (known after apply)
      + ssh_user     = "root"
      + sshkeys      = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDVKCfpeIMg7GS3Pk03ZAcBWAeDZ+AvWk2k/pPY0z8MJ3YAbqZkRtSK7yaDgJV6Gro7nn/TxdJLo2jEzzWvlC8d8AEzhZPy5Z/qfVVjqBTBM4H5+e+TItAHFfaY5+0WvIahxcfsfaq70MWfpJhszAah3ThJ4mqzYaw+dkr42+a7Gx3Ygpb/m2dpnFnxvXdcuAJYStmHKU5AWGWWM+Fm50/fdMqUfNd8MbKhkJt5ihXQmZWMOt7ls4N8i5NZWnS9YSWow8X/ENOEqCRN9TyRkc+pPS0w9DNi0BCsWvSRJOkyvQ6caEnKWlNoywCmM1AlIQD3k4RUgRWe0vqg/UKPpH3Z root@terraform"
      + target_node  = "branly"
      + vcpus        = 0
      + vlan         = -1
      + vmid         = 132

      + disk {
          + backup       = false
          + cache        = "none"
          + format       = "raw"
          + id           = 0
          + iothread     = false
          + mbps         = 0
          + mbps_rd      = 0
          + mbps_rd_max  = 0
          + mbps_wr      = 0
          + mbps_wr_max  = 0
          + replicate    = false
          + size         = "32G"
          + storage      = "proxmox"
          + storage_type = "cephfs"
          + type         = "virtio"
        }
      + disk {
          + backup       = false
          + cache        = "none"
          + format       = "raw"
          + id           = 1
          + iothread     = false
          + mbps         = 0
          + mbps_rd      = 0
          + mbps_rd_max  = 0
          + mbps_wr      = 0
          + mbps_wr_max  = 0
          + replicate    = false
          + size         = "100G"
          + storage      = "proxmox"
          + storage_type = "cephfs"
          + type         = "virtio"
        }

      + network {
          + bridge    = "vmbr443"
          + firewall  = false
          + id        = 0
          + link_down = false
          + macaddr   = (known after apply)
          + model     = "virtio"
          + queues    = -1
          + rate      = -1
          + tag       = -1
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Changes to Outputs:
  + clearly-defined_summary = (known after apply)

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.

terraform apply happy as well:

clearly-defined_summary =
hostname: clearly-defined
fqdn: clearly-defined.internal.staging.swh.network
network: ip=192.168.130.200/24,gw=192.168.130.1 macaddrs=B6:C6:2E:[D3](https://forge.softwareheritage.org/D3 'view original for D3 on Phabricator'):60:B2

---

Migrated from D4754 (view on Phabricator)