Make the init container fail on any initialization failure

[ypc-faros]

Description

Make the init container fail on any initialization failure.

Scenarios verified:

• Unreachable db, Airbyte, Hasura or Metabase webapps.
• Error in Flyway migration (typo in a table name in a foreign key reference).
• Error in Airbyte/Hasura/Metabase initialization scripts (I added a throw to the top of main)

Fixes #159 (I verified that docker-compose up exit code is 1 in my local. I expect the GHA to fail and hence stop the release)

Type of change

(Delete what does not apply)

• New feature (non-breaking change which adds functionality)

Checklist

(Delete what does not apply)

• Have you checked to there aren't other open Pull Requests for the same update/change?
• Have you lint your code locally before submission?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you successfully run tests with your changes locally?

[thomas-gerber]

• Error in Airbyte/Hasura/Metabase initialization scripts (I added a throw to the top of main)

where is the throw?

[ypc-faros]

• Error in Airbyte/Hasura/Metabase initialization scripts (I added a throw to the top of main)

where is the throw?

That's what I did to tests what happens when the Typescript programs throw :)

[tovbinm]

nice!