Prevent use of Rolling Update if any Index Set has 0 Replica shards

We offer two methods of updating Data Node - Cluster Restart, and Rolling Upgrade.

Rolling Upgrade only works correctly if all Index Sets have a replica set >0. Any Index lacking replica shards will become unavailable when the Data Node hosting the shards goes offline, which will move Opensearch into Red status and prevent traffic being unloaded into OS (so causing Graylog Journal to grow).

We should prevent the user from starting a Rolling Upgrade when any Index Sets have a replica shard count of 0.

We can allow the user to navigate to the tab, but not to start the upgrade. We should put a red banner on the page explaining why the buttons are grayed out.