fix: Temporary ignore some DNS checks

[smolin-de]

There are several open issues related to DNS. DNS setup needs to be verified. We ignore some DNS check results for now, because of issue 166, 182.

[AmadeusPodvratnik]

@smolin-de I looked into #182 and it looks to me that using

• { role: check_dns, when env.bastion.options.dns is defined and env.bastion.options.dns} instead of
• check_dns
  in 5_setup_bastion playbook will solve the issue of an external dns, correct?
  But looking in Playbook 5 says dig validation of DNS fails, but dig lookup commands are succesful #166 we can fix it differently...
  As far as I understood the issues is, that the output of services_lookup.stdout is different from bastion ip (check in check-dns role: (env.bastion.options.loadbalancer.on_bastion == True) and (env.bastion.networking.ip != services_lookup.stdout)).
  If we would like to have an api dns check we need to introduce the IP of the dns server (in all.yaml).

[AmadeusPodvratnik]

Pls change the role call in 5_setup_bastion playbook:
{ role: check_dns, when env.bastion.options.dns is defined and env.bastion.options.dns} instead of
check_dns

[AmadeusPodvratnik]

Looks good, thank you!