Support Pauseable Upgrades in Storm Service

### 🚀 Feature Description and Motivation

Currently, Storm Service lacks controlled upgrade capabilities such as pausing, resuming, or rolling back deployments during the upgrade process. This limitation makes it challenging to implement risk-aware deployment strategies (e.g., canary releases, blue-green deployments) and introduces operational risks when deploying changes to production environments.

This feature request proposes adding upgrade orchestration capabilities similar to [Argo Rollouts](https://argoproj.github.io/argo-rollouts/), including the ability to:

- Pause upgrades at predefined stages for manual verification
- Automatically roll back on failed health checks
- Perform canary releases with traffic routing
- View upgrade progress and status

### Use Case

Support production-grade upgrade experiences

### Proposed Solution

_No response_

The issue does not name any implementation files, tests, or entry points. Start by locating Storm Service's upgrade orchestration, health-check, and traffic-routing paths, then define the scope and acceptance criteria for pausing, resuming, rollback, canary routing, and progress reporting.

Written by the indexing model from the issue text.