Enhancement: This PR adds the `loopback` device to `black_list_names` when deleting all profiles except the ones explicitly included in the ansible playbook Reason: Adding an entry without a name and `persistent_state: absent` to the `network_connections` variables would trigger a `changed` state in one of the tasks ``` TASK [network : Configure networking connection profiles] ********************** changed: [hostname] ``` This was because the profile `loopback` device was being removed and then automatically recreated by the system. Result: Now the loopback profile is kept and the state is not reported as `changed`: ``` TASK [network : Configure networking connection profiles] ********************** ok: [hostname] ``` Issue Tracker Tickets (GitHub issue): #689 ## Summary by Sourcery Keep the loopback network profile from being deleted when purging absent profiles to prevent false-positive changes in Ansible playbooks Bug Fixes: - Prevent Ansible from reporting a changed state by avoiding removal and automatic recreation of the loopback profile Enhancements: - Add "lo" (loopback) to the blacklist when deleting all non-explicit network profiles