Updating alerts can redeploy prometheus if the version has changed in values.yaml (or if chart version has updated)

This happens for the same reason as #32844 (closed) and should be taken into consideration when updating the prometheus chart (ideally by fixing the underlying bug).

To elaborate, the problematic flow is:

1. user installs prometheus
2. gitlab changes hardcoded versions in values.yaml (e.g. by removing them)
3. user changes an alert on one of their metrics in Operations > Metrics

Expected behavior: Only the alert they changed should be affected

Actual behavior: Prometheus gets redeployed with whatever version is in values.yaml (or the chart default)