Return error when service update triggers rollback

[Best2Two]

Return error when service update triggers rollback

When a service update fails and triggers a rollback, the command now
exits with code 1 instead of 0, allowing deployment tools to detect
failures.

Fixes #6752

- What I did
Modified the ServiceProgress function in cli/command/service/progress/progress.go to return an error when automatic rollback occurs after a failed update, instead of returning success.

- How I did it
Added a check after service convergence verification. When the rollback flag is true (indicating the update was rolled back), the function returns an error, causing the CLI to exit with code 1.

- How to verify it

1. Initialize a swarm: docker swarm init
2. Deploy a stack with a healthy service using the docker-compose.yml from issue Unable to detect rollbacks during "docker stack deploy" in CI/CD #6752 (with exit 0 healthcheck)
3. Update the compose file to use exit 1 in the healthcheck
4. Run docker stack deploy --detach=false -c docker-compose.yml test-rollback
5. The service will rollback and the command should exit with code 1
6. Verify with echo $?

- Human readable description for the release notes

Fix `docker stack deploy` to exit with error code when service update triggers rollback

- A picture of a cute animal (not mandatory but encouraged)
🐳