kratos: use more up-to-date image

[hugotiburtino]

We are using our own image for now (see https://github.com/serlo/kratos, branch next). Since the sha algorithm for password is merged into main branch of kratos, we can now use a more up-to-date image. That way we are going to be quite sure that the oficial build also works at us without surprises. We have already in our registry a more up-to-date image, eu.gcr.io/serlo-shared/kratos:0.11.1-custom.

Steps

• create a branch in serlo/infrastructure-env-staging, update the image there.
• the new image will lead to strategy code at the verification as default. Since we don't support it yet, we have to stick to the magic link strategy. Create a branch here, add use: link to the kratos.config.selfservice.flow.verification
• In order to test before creating a tag, change the source from module kratos at env-staging to use a relative path to your local modules-shared
• apply changes, test throughly all flows in staging, commit and open a PR

[hugotiburtino]

M4.1 SSO ist im Test-System nutzbar

[AndreasHuber]

https://github.com/serlo/infrastructure-env-staging/pull/34