device: after stage1 call stage2 synchronously

We know we are ready and in a situation where we can handle state changes.
Don't schedule stage2 in an idle handler, just invoke it directly.
17 jobs for th/act-stage1-re-entrant in 40 minutes and 7 seconds (queued for 2 seconds)
Status Job ID Name Coverage
  Test
passed #529005
allowed to fail
checkpatch

00:01:03

manual #529010
allowed to fail manual
t_centos:7.5.1804
passed #529011
t_centos:7.6.1810

00:29:00

passed #529017
t_debian:10

00:26:58

passed #529016
t_debian:9

00:29:53

passed #529019
t_debian:sid

00:22:13

manual #529018
allowed to fail manual
t_debian:testing
passed #529006
t_fedora:28

00:32:12

passed #529007
t_fedora:29

00:40:04

passed #529008
t_fedora:30

00:32:24

manual #529009
allowed to fail manual
t_fedora:rawhide
passed #529012
t_ubuntu:16.04

00:22:22

passed #529013
t_ubuntu:18.04

00:30:11

manual #529015
allowed to fail manual
t_ubuntu:devel
manual #529014
allowed to fail manual
t_ubuntu:rolling
 
  External
failed https://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/beaker-NetworkManager-gitlab-trigger-code-upstream/607/

failed https://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/beaker-NetworkManager-gitlab-trigger-code-upstream/607/

05:53:25