[Feature]: Reboot Exemptions

What is the installation method of your PatchMon server?

Docker

What is the version of your PatchMon server?

2.0.2

Briefly describe the feature

Supporting disabling auto-reboot for given policies or groups.

Detailed description

Having the ability to indicate that a given host should not be rebooted by PatchMon. A couple of different approaches could be employed:
A - Host-level exemption that will work with any policy. (With support to specify during auto-enrollment)
B - Group-level for less tedious, but less granular controls
C - Policy-level *basically same as Group

Why is this useful?

In certain workloads, it is imperative that you properly spin down the service before rebooting, or that multiple boxes do not both attempt to do so simultaneously.

3 examples I can give:
A - With Kubernetes, the proper sequence is to cordon and drain the node, reboot, then uncordon. This allows containers to cleanly exit and redeploy onto another node, allowing for near 100% uptime of even single instance services.
B - With Quorumed Clusters, Certain checks have to be made to ensure that the remaining cluster will survive if a given voting member is not available. Rolling one at a time without these checks works if things go well, but if members are not contributing prior to starting or if the reboot fails to bring back that member, then the rest of the nodes would not know to stop.
C - Disconnected update and reboot schedules are sometimes needed for critical systems. Some systems need reboots on unique schedules due to non-technical reasons.

Disabling reboots would allow for these processes to be handled by tools developed for these special conditions. (i.e. Kured for Kubernetes)