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-base/tasks/setup_server_base.yml

@@ -23,7 +23,6 @@
       - bash-completion
       - docker-ce
       - docker-python
-      - firewalld
       - ntp
       - fuse
     state: latest
@@ -67,13 +66,6 @@
     update_cache: yes
   when: ansible_os_family == 'Debian'
 
-- name: Ensure firewalld is started and autoruns
-  service:
-    name: firewalld
-    state: started
-    enabled: yes
-  when: ansible_os_family == 'RedHat'
-
 - name: Ensure Docker is started and autoruns
   service:
     name: docker