fix(helm): Exit init script immediately on error

[sourcecode-glitch]

SUMMARY

This adds set -eu to the init script. With this the script will exit immediately when it encounters an error or an unset variable.

TESTING INSTRUCTIONS

In order to test that this works you will need a k8s environment. One way to test this is to manually add an error into the init script by including an invalid command (just make sure that the last command in the script is still a working command). Then start a helm deployment. Without this PR the init job will be marked as success despite the error. With this PR applied the init job will be marked as failed.

ADDITIONAL INFORMATION

• Has associated issue: Fixes [Helm Chart] Init job marked as success despite errors #16757
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

ADDITIONAL THOUGHTS

I personally think failing when an error occurs should be the default behavior. However, I could see that some people might prefer it if the script does not fail and instead tries the remaining init steps. If this is wanted I could add a flag to the init config in values.yaml so that users can easily select the behavior they want. Let me know if this is wanted or if this PR is ok as it is. I personally don't really think it's worth including a switch, because with the current behavior you would need to read the whole init job logs in order to know if there were any problems.

[craig-rueda]

This requires a version bump

[sourcecode-glitch]

Bumped helm chart version to 0.3.9 and rebased onto current master (CI didn't seem to work on the older master commit that this was based on before)