reboot-limit: simplify what gets selected

If you try to take the reboot-limit workflow for a spin right now
you will run into a conflict with networkd.service and the bringup
we have on debian-testing. I have narrowed this down to the few extra
selects we do, and the reason is that we have not seen these issues
before on our CI. Testing with these disabled fixes the issue so just
disable those selects as we already do enough of a good job of enabling
sensible defaults.

Signed-off-by: Luis Chamberlain <[email protected]>

Author: mcgrof

workflows/demos/reboot-limit/Kconfig

@@ -1,9 +1,5 @@
 config WORKFLOWS_REBOOT_LIMIT
 	bool "Reboot-limit"
-	select KDEVOPS_TRY_REFRESH_REPOS
-	select KDEVOPS_TRY_INSTALL_KDEV_TOOLS
-	select KDEVOPS_DEVCONFIG_ENABLE_CONSOLE
-	select KDEVOPS_DEVCONFIG_ENABLE_SYSTEMD_WATCHDOG
 	help
 	  If you are doing kernel tests which includes a reboot, along the way,
 	  or if you do a reboot after a series of tests, you may want to first