fail2ban role corrupts configuration.yaml if reverse proxy container is not running

[jhampson-dbre]

If the reverse proxy container is not running (e.g. after restarting home assistant), the container info will be found, but it will not have an IP address assigned yet and set a blank list entry for trusted_proxies: in configuration.yaml. Ideally, if the reverse proxy addon is not running, we would wait for some time for it to start (or maybe try to start it?), and then either fail the task or bypass modifying the configuration.yaml (although that could leave it in a state with incorrect/no trusted_proxies defined).

Either way, fail2ban role should handle this scenario more gracefully than it does currently.