Support Rolling Upgrades for MMS3/NooBaa Clusters

Add support for performing rolling upgrades of MMS3/NooBaa cluster nodes while maintaining availability of the S3 service.

MMS3/NooBaa currently relies on a shared filesystem for configuration and cluster-related data. The current architecture and upgrade process do not provide a clear or supported method for upgrading individual nodes sequentially while the remaining nodes continue serving production workloads.

Because this is a production system, taking the entire cluster offline for maintenance or software upgrades introduces significant operational risk and service disruption. A supported rolling-upgrade process would allow administrators to place one node at a time into maintenance, upgrade it, validate its health, and return it to service before proceeding to the next node.

We recognize that MMS3/NooBaa nodes may also host additional storage protocols and services, which may add complexity to node-level maintenance. The requested enhancement could therefore include coordinated service management, node-draining capabilities, compatibility checks, and documented procedures for safely upgrading nodes without disrupting the remaining cluster.

This capability would improve service availability, reduce planned downtime, and make MMS3/NooBaa more suitable for environments with strict production uptime and maintenance requirements.