Feature extra env init container

[kenzaboussaoud8]

This PR adds support for the extraEnvVars section to the migrations section of the api.

[vercel]

Someone is attempting to deploy a commit to the neosync Team on Vercel.

A member of the Team first needs to authorize it.

[nickzelei]

Hey, thanks for the PR! Left a comment.

You'll also want to run make helm/docs to generate the helm documentation and get that added to the commit.

[nickzelei]

Separately, curious as to what your usecase is for this feature addition?

[kenzaboussaoud8]

Separately, curious as to what your usecase is for this feature addition?

Hello Nick, this is to simplify our deployment process by reducing the need for manual patches. Specifically, we need to avoid applying patches for db credentials.

[nickzelei]

Separately, curious as to what your usecase is for this feature addition?

Hello Nick, this is to simplify our deployment process by reducing the need for manual patches. Specifically, we need to avoid applying patches for db credentials.

Hmm, still not super clear. The db migrations container is fully configurable via the helm chart through the values. What are you looking to specify in the extra that isn't already available to configure through the helm chart as-is today?

[nickzelei]

I tried running this but the helm output failed due to indentation I believe. I think it might need to be indented one more section so that it appears underneath the env.

[nickzelei]

Hey @kenzaboussaoud8 - I went ahead and took this over the line. Since outside collabs branches are slightly different, i wasn't able to push to this pull request directly.
You can see my final PR here: #2717

Thank you for the contribution!