Related to T3705

Related to T3630

Related to T3487

Related to T3487

Need to change the way the puppet data is mounted inside the VM
because nfs on udp is disabled in the default bullseye kernel.
cf https://github.com/hashicorp/vagrant/issues/10345

Related to T3497

Related to T3497

One with each a different role in puppet

Related to T3462

- use the same hostname as in production
- add the self signed certificate to simulate certmanager

This adds the new nodes search-esnode[4-6]

Related to T3041

Related to T3041

This is hard to maintain as it is as most declarations are the same with slight changes
over memory, hostname, ip, etc...

This extracts the difference into a hashtable and map over said hashtable to declare the
vm instead.

Related to T3325

Related to T3325

This won't work as that iso did not get published in the end because unneeded.

Related to T3325

Run the provisionning of the facts first because if something is going
wrong during the first puppet apply, the facts are not configured

Related to T3325

Related to T3325

For unexpected reason, when puppet master is running through passenger
the `environmentdir` configurration is ignored and the environments
not found (for example staging).

Related to T3325

This actually installs the /etc/facts/fact.d/*.txt facts as files on the machine.

Related to T3325

Related to T3325

Temporary hack to install postgresql prior to puppetdb.

Related to T3325

That will avoid the need to install rsync altogether

Related to T3325

Related to T3325

Or the default value targets an inexistant /var/cache/puppet folder:

```
==> pergamon: Error: Evaluation Error: Error while evaluating a Function Call, Could not find any files from
/var/cache/puppet/ssl/certs/pergamon.softwareheritage.org.pem (file:
/tmp/vagrant-puppet/environments/production/site-modules/profile/manifests/puppet/master.pp,
line: 29, column: 30) on node pergamon.softwareheritage.org
```

or

```
==> pergamon: Error: Removing mount "le_certs": /var/cache/puppet/letsencrypt_exports does not exist or is not a directory
```

Related to T3325

This fails otherwise [1]

Either that or redo the debian image so it's installed there.

[1]
```
==> pergamon: Running provisioner: shell...
    pergamon: Running: /tmp/vagrant-shell20210518-14488-1xk5s1k.sh
    pergamon: sudo
    pergamon: :
    pergamon: rsync: command not found
```

Related to T3325

- change le_certs mount points to match agent/master configuration
- add puppet master certificate provisioning on pergamon
- increase pergamon memory to be able to run puppetdb

Related to T3325

change the le_certs fileserver configuration to match the reality.
It's needed reduce the difference between the agents and the puppet
master

Related to T3325