[feat] argo-rollouts should restart when changes are made to the configmap

[DerekTBrown]

Is your feature request related to a problem?

• The argo-rollouts-config ConfigMap contains various options that can only be modified upon pod restart.
• Currently, changing the ConfigMap does not trigger a pod restart.
• This is problematic for a number of reasons:
  1. A user needs to manually churn all of the pods for changes to take effect, which is cumbersome.
  2. If the user introduces a bad change, and forgets to manually churn all the pods, this becomes a ticking time-bomb, since the changes will take effect when the pods next restart of their own accord

Related helm chart

argo-rollouts

Describe the solution you'd like

The idiomatic solution is to include a hash of the ConfigMap as part of the Deployment spec. Thus, if the ConfigMap changes, the Deployment will automatically be updated.

Describe alternatives you've considered

No response

Additional context

No response