This implementation doesn't work properly after testing.
The iptable configuration didn't allow for changing the VPN state
without running into networking issues.

Either have to change the VPN by running the role, which is inconvenient
or reimplement the role differently to allow for control over
network/interfaces

This reverts commit 06e686bc12ee10697431f056efbaecdcba1681d2.

This reverts commit fdd0b5b58f0ebd39ad05e2dcb17faa6603145f97.

As the role now functions as a gateway and not just a wireguard gateway
it's better name for clarity

This allows forwarding the traffic through the pi (similar to how the
VPN is routing all the traffic using it's iptables)

This means that the role is more of a general gateway
When the vpn is activated it handles routing all the traffic through it
This commits provide the same functionality when the VPN isn't active

Allow the wireguard_gateway to configure all forwarding for all the
interfaces available for the connections