Bug: init job succeeds even if failed running "sql"

Chart version: 12.0.3
helm version: v3.14.2

Init job starts early and is unable to connect to DB but the container exits with code 0 and the job does not restart.

Logs attached:

```
ERROR: cannot dial server.
Is the server running?
If the server is running, check --host client-side and --advertise server-side.

dial tcp 12.34.56.78:26257: connect: connection refused
Failed running "sql"
Provisioning completed successfully
```

Jira issue: HELM-14

Start by reproducing the init job with chart version 12.0.3 and Helm v3.14.2 while the database is unavailable, then inspect how the job handles a failed `sql` command. Done means the failed command produces a failing job status and the chart no longer reports provisioning as successful.

Written by the indexing model from the issue text.