Do not fail when spawned LXC is supposed to not be in the same subnet like controlhost

[bellackn]

Is your feature request related to a problem? Please describe.
When you deliberately start an LXC in a subnet that your Ansible controlhost cannot reach, the role will always fail at the "Wait until sshd of LXC '{{ item.hostname }}' is ready" task.

Describe the solution you'd like
The role should check the network interfaces that your Ansible host is in and then compare it with the address you want to assign to the container. If it's clear beforehand that you won't be able to access the host, this task should be skipped.

Describe alternatives you've considered
You could define a default variable with your IP subnet. Then compare this variable to the IP address that you assign to the LXC.