Do not force firewalld on people

In most cases, there's not really a need to touch the system
firewall, as Docker manages iptables by itself
(see https://docs.docker.com/network/iptables/).

All ports exposed by Docker containers are automatically whitelisted
in iptables and wired to the correct container.

This made installing firewalld and whitelisting ports pointless,
as far as this playbook's services are concerned.

People that wish to install firewalld (for other reasons), can do so
manually from now on.

This is inspired by and fixes #97 (Github Issue).

roles/matrix-coturn/tasks/setup_coturn.yml

@@ -54,20 +54,6 @@
     daemon_reload: yes
   when: "matrix_coturn_enabled and matrix_coturn_systemd_service_result.changed"
 
-- name: Allow access to Coturn ports in firewalld
-  firewalld:
-    port: "{{ item }}"
-    state: enabled
-    immediate: yes
-    permanent: yes
-  with_items:
-    - '3478/tcp'
-    - '3478/udp'
-    - '5349/tcp'
-    - '5349/udp'
-    - "{{ matrix_coturn_turn_udp_min_port }}-{{ matrix_coturn_turn_udp_max_port }}/udp" # TURN
-  when: "matrix_coturn_enabled and ansible_os_family == 'RedHat'"
-
 # This may be unnecessary when more long-lived certificates are used.
 # We optimize for the common use-case though (short-lived Let's Encrypt certificates).
 # Reloading doesn't hurt anyway, so there's no need to make this more flexible.