pyrocufflink-dns: Cloudflare over ProtonVPN

This commit adds a new playbook, `protonvpn.yml`, and its supporting
roles *strongswan-swanctl* and *protonvpn*.  This playbook configures
strongSwan to connect to ProtonVPN using IPsec/IKEv2.

With this playbook, we configure the name servers on the Pyrocufflink
network to route all DNS requests through the Cloudflare public DNS
recursive servers at 1.1.1.1/1.0.0.1 over ProtonVPN.  Using this setup,
we have the benefit of the speed of using a public DNS server (which is
*significantly* faster than running our own recursive server, usually by
1-2 seconds per request), and the benefit of anonymity from ProtonVPN.

Using the public DNS server alone is great for performance, but allows
the server operator (in this case Cloudflare) to track and analyze usage
patterns.  Using ProtonVPN gives us anonymity (assuming we trust
ProtonVPN not to do the very same tracking), but can have a negative
performance impact if its used for all Internet traffic.  By combining
these solutions, we can get the benefits of both!

group_vars/pyrocufflink-dns/main.yml

@@ -1,3 +1,8 @@
+protonvpn_tunnel: 1.1.1.1,1.0.0.1
+named_forward_only: true
+named_forwarders:
+- 1.1.1.1
+- 1.0.0.1
 named_listen:
 - addresses:
   - any

group_vars/pyrocufflink-dns/secrets

@@ -0,0 +1,10 @@
+$ANSIBLE_VAULT;1.1;AES256
+34303664613262623439636133393766306638343261373633633136323562643761383039376565
+3339663861393833666164633136373966336630346434660a616231343233653366393666336339
+31643862626561643636343666313539343933353138336166373335323830643361303362353864
+3934633236313862620a616561393265336138383339393063613631633030646633363736333139
+37343664333063616430366534633366383565613530613439313732333232363336626236613235
+35636165386565633466306638656662323739396535386565316662353735386466643038613337
+61363936326363323730393132313532326336373761653237623963363163373633623737643434
+66386234303265343262333566356566626531633665626464343962633337373962396533343432
+6163