Move kratos-automigrate under kratos init-containers

[niravparikh05]

Describe the issue you're facing

• While upgrading kratos helm chart which will be defaulted to the corresponding app version cause issue with health probe if the migration is run on a different / lower version.

Currently kratos-automigrate is present as part of paralus init container and kratos binary is packaged with it ( now if there is a mismatch between kratos app version here and one helm chart uses, health probe fails to bring kratos pod up ), explore the possibility of moving it as kratos init container to avoid this dependency

[akshay196]

Backstory: Kratos-automigrate is part of paralus init container because paralus db-migration is dependent on kratos tables. Parlaus db-migration fails unless kratos migration is successfully completed.

Few rough ideas to resolve this issue:

1. Remove kratos and paralus migration coupling. This might be a right step for project maintainability because it decouples Kratos and Paralus migrations.
2. Let paralus init container decide kratos migration based on kratos version in use. This can be accomplished using a simple bash-script that reads kratos version, download respective binary and perform migration.