## Problem

PR #26194 added `--use_v2_migration_resolver` to address the diff-and-force schema-thrashing bug tracked in #22998. The flag works as advertised. However, the bundled Helm chart (`deploy/charts/litellm-helm`) hasn't been updated to take advantage of it:

- `deploy/charts/litellm-helm/templates/migrations-job.yaml` runs `command: ["python", "litellm/proxy/prisma_migration.py"]`. - `litellm/proxy/prisma_migration.py` calls `run_server(["--skip_server_startup"], standalone_mode=False)` with no flag and no envvar fallback (the click option at `proxy_cli.py` ~line 581 has no `envvar=`). - There is no `command:`/`args:`/`extraArgs:` value on the chart's migration job to override this.

Net effect: any operator using the official chart silently gets the v1 resolver, even on the LiteLLM versions that ship the v2 fix. The bug from #22998 keeps reproducing under the chart's default rolling-deploy strategy.

## Concrete repro (just lived this)

Bumped the chart's `image.tag` from `main-v1.82.3` → `v1.83.14.rc.1`. The migration Helm-hook job ran and reported success. `_prisma_migrations` showed all 11 new migrations in the batch as `finished_at = <deploy time>` with no `rolled_back…