change hook weight to -1 (job has to run after config maps placed)

[masbarnes]

Change hook weight for the job to -1 (the config maps with hook weight -2 need to be created in order for the job to succeed)

Greptile Summary

This PR adjusts the Helm pre-install/pre-upgrade hook weight for database_init_job.yaml from -2 to -1, ensuring the database initialization job runs after config maps (which carry hook weight -2) are fully created. The change addresses a real ordering issue where the init job previously ran in parallel with config map creation.

The weight adjustment is sound and solves the immediate problem stated in the PR: ensuring config maps are ready before the job starts.

Confidence Score: 4/5

• The change safely resolves the config map ordering issue without introducing verified problems.
• The PR makes a focused, intentional change to fix a specific ordering bug. The new weight -1 ensures the init job runs after all weight -2 hooks (config maps) complete, which is the stated goal. No concrete issues are introduced by this change.
• No files require special attention

_{Last reviewed commit: c6a75ba}