fix: run `extraInitContainers` before migration

[cschmatzler]

In values.yaml, the deployment.extraInitContainers value is documented as follows:

These are processed before the migration init container.

In the template itself, they were added after the migration container, though. Since Kubernetes runs init containers in the order they were defined, and each one of them has to be successful in order for the next to be started, this can block setups where there's an extra init container that sets up the database.

See also the relevant Kubernetes documentation:

If you specify multiple init containers for a Pod, kubelet runs each init container sequentially. Each init container must succeed before the next can run. When all of the init containers have run to completion, kubelet initializes the application containers for the Pod and runs them as usual.

Related Issue or Design Document

Init containers were added in an order that contradicts the documentation in values.yaml.

Checklist

• [x] I have read the contributing guidelines and signed the CLA.
• [ ] I have referenced an issue containing the design document if my change introduces a new feature.
• [x] I have read the security policy.
• [x] I confirm that this pull request does not address a security vulnerability. If this pull request addresses a security vulnerability, I confirm that I got approval (please contact security@ory.sh) from the maintainers to push the changes.
• [ ] I have added tests that prove my fix is effective or that my feature works.
• [ ] I have added the necessary documentation within the code base (if appropriate).

[cschmatzler]

Hey! Thanks for the quick review. I have applied your suggestion and also applied the same change to the Keto and Hydra charts.

Let me know if I missed anything, since I'm not too familiar with all the components yet.

Cheers!