Special handling of autofailover for bucket restarts due to config change

It's not very often, but occasionally a customer will need to change a bucket parameter that requires the bucket to be restarted (ie. ejection policy).

When auto-failover is enabled, and email alerts are set to go out, this can result in a flood of false-positive alerts...especially on a large cluster.

From a user experience perspective, it would be an improvement for us to have a special case to handle intentional bucket restarts and prevent auto-failover from kicking in.