team: perform cleanup immediately when connecting to teamd fails

When NM fails to connect to teamd during an activation, it sets the
device state to FAILED. Eventually the device will become DISCONNECTED
and will call the ->deactivate() method that will perform the cleanup
of timers, teamd process and teamdctl instance.

However, in this way, when the device is DISCONNECTED timers are still
armed and can be triggered in the wrong state. Instead, perform the
cleanup immediately on failure.

https://bugzilla.redhat.com/show_bug.cgi?id=1856723
21 jobs for bg/rh1856723 in 34 minutes and 50 seconds (queued for 3 seconds)
Status Job ID Name Coverage
  Test
passed #3638601
checkpatch

00:01:10

manual #3638608
allowed to fail manual
t_centos:7.5.1804
manual #3638609
allowed to fail manual
t_centos:7.6.1810
manual #3638610
allowed to fail manual
t_centos:7.7.1908
manual #3638611
allowed to fail manual
t_centos:7.8.2003
manual #3638612
allowed to fail manual
t_centos:8.1.1911
manual #3638618
allowed to fail manual
t_debian:10
manual #3638617
allowed to fail manual
t_debian:9
manual #3638620
allowed to fail manual
t_debian:sid
manual #3638619
allowed to fail manual
t_debian:testing
manual #3638602
allowed to fail manual
t_fedora:28
manual #3638603
allowed to fail manual
t_fedora:29
manual #3638604
allowed to fail manual
t_fedora:30
passed #3638605
t_fedora:31

00:34:49

manual #3638606
allowed to fail manual
t_fedora:32
manual #3638607
allowed to fail manual
t_fedora:rawhide
manual #3638613
allowed to fail manual
t_ubuntu:16.04
manual #3638614
allowed to fail manual
t_ubuntu:18.04
manual #3638616
allowed to fail manual
t_ubuntu:devel
manual #3638615
allowed to fail manual
t_ubuntu:rolling
 
  External
canceled https://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/beaker-NetworkManager-gitlab-trigger-code-upstream/1667/

147:20:58