[BUG] systems with foreman_boot do not reboot into kickstart during M&R

[sadsfae]

It appears that systems already in foreman_boot or the "Foreman" style boot order do not issue a proper power off / power on to initiate kickstart. They simply wait for validate_env to pick this up and do it. This adds considerable time to releasing systems as they are simply sitting there powered on.

• Systems during M&R that have existing OS, are accessible (confirmed Foreman boot order)

-=>>for host in $(quads --cloud-only --cloud cloud55); do printf "$host  "; ssh -o Connecttimeout=5 root@$host "cat /etc/redhat-release" 2>/dev/null || echo " kicking"; done
d41-h08-000-r660example.com  Red Hat Enterprise Linux release 9.4 (Plow)
d41-h09-000-r660example.com  Red Hat Enterprise Linux release 9.4 (Plow)
d41-h10-000-r660example.com  Red Hat Enterprise Linux release 9.4 (Plow)
d41-h11-000-r660example.com  Red Hat Enterprise Linux release 9.4 (Plow)
d41-h12-000-r660example.com  Red Hat Enterprise Linux release 9.4 (Plow)
d41-h13-000-r660example.com  Red Hat Enterprise Linux release 9.4 (Plow)
d41-h14-000-r660example.com  Red Hat Enterprise Linux release 9.4 (Plow)
d41-h15-000-r660example.com  Red Hat Enterprise Linux release 9.4 (Plow)
d41-h16-000-r660example.com  Red Hat Enterprise Linux release 9.4 (Plow)
d41-h17-000-r660example.com  Red Hat Enterprise Linux release 9.4 (Plow)

• We can see they are marked for build but need a proper nudge to either reboot or chassis power off / on to initiate kickstarting in a timely and intended fashion.

-=>>for h in $(quads --cloud-only --cloud cloud55) ; do echo $h === $(hammer host info --name $h | grep -i build) ; done
d41-h08-000-r660example.com === Build Status: Pending installation Build: yes
d41-h09-000-r660example.com === Build Status: Pending installation Build: yes
d41-h10-000-r660example.com === Build Status: Pending installation Build: yes
d41-h11-000-r660example.com === Build Status: Pending installation Build: yes
d41-h12-000-r660example.com === Build Status: Pending installation Build: yes
d41-h13-000-r660example.com === Build Status: Pending installation Build: yes
d41-h14-000-r660example.com === Build Status: Pending installation Build: yes
d41-h15-000-r660example.com === Build Status: Pending installation Build: yes
d41-h16-000-r660example.com === Build Status: Pending installation Build: yes
d41-h17-000-r660example.com === Build Status: Pending installation Build: yes

[sadsfae]

Likely we''re missing the directive to call await badfish.reboot_server(graceful=False) as we only do this if QUADS thinks it needs to change the boot order to match Config["foreman_default_boot_order"]

https://github.com/redhat-performance/quads/blob/latest/src/quads/tools/move_and_rebuild.py#L274

@kambiz-aghaiepour @grafuls