Tracer rex templates don't handle reboot properly
Calling reboot directly causes troubles both in ssh and ansible templates. Rex has special templates for dealing with it better
in in ssh templates, and in ansible, we should probably be using `reboot` module.
Steps to Reproduce:
1. Have system registered with remote execution SSH key deployed and with updated kernel
2. Go to Content host details -> Traces -> check "kernel" -> Restart Selected
System is restarted, but ReX job fails
Job should pass if restart worked (it worked for me) and trace item should go away.
Fixes #26185 - fix traces action when upgrading kernel
Calling reboot directly doesn't play nicely in SSH neither does in
In SSH scripts, we need to call the power template to let the rex know
we expect the reboot. Although, even after that the traces would not
be updated until katello-tracer-upload is called.
Ansible allows us to reboot and call katello-tracer-upload afterwards,
therefore it should be our default preference for performing the tracing
actions. For this reason, I've added a migration to use the Ansible
After this, I was able to upgrade new kernel, see the traces and after
using the UI to restart, I've eventually saw getting the traces away.