### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

If running Prisma schema migration via `migrationJob.enabled: true` with one of `migrationJob.hooks.helm.enabled: true` or `migrationJob.hooks.argocd.enabled: true`, the Job template adds the appropriate annotations for the hook.

If `serviceAccount.create: true` is also set, the migration Job pod may fail to start if the required ServiceAccount has not been created yet (on initial install).

While the chart does allow the user to manually add the same set of hook annotations under `serviceAccount.annotations`, the chart template should do that automatically.

### Motivation, pitch

This issue should really be a bug, even though a workaround exists. To ensure that the migration Job runs without failure, the ServiceAccount template should add the same set of hook annotations (if any) to the Job template.

### What part of LiteLLM is this about?

Other

### LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

### Twitter / LinkedIn details

_No response_