The reason the idempotent test fails is the following:

- 1st run: wireguard role deploys all the configured VPN connections
- 1st run: wg_portal updates the file permissions /etc/wireguard (ACLs)
- 2nd run: wireguard sees the file changed, deploys again (idempotent failure)

When a wireguard configuration gets removed from the group/host
variables, the role now removes them and make sure only the files found
in the vars are the ones to be configured on the hosts

It's only necessary to stop the VPN to set another one running instead
(as the configurations are not built to stack VPN although possible)

The idempotent test is only failing on the second run,
the reason is, on the first run the wireguard files are created with
default permissions, then the wg_portal role update the ACL.

On the second run, the wireguard role recognizes the difference in the
permissions, and update the files (expectedly), the default ACL then
takes place and set the permissions correctly with ACLs

On any successive run, the role is idempotent and doesn't update the
files again.

Since the ACL fix probably fixed this one too