fix(docker): run migrations after postgres is up & running

[TheJoin95]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Adding a healthcheck which is going to be useful on a fresh install or slow docker-compose booting time.
As per now the migration container won't wait the Postgres service to be up & running so it won't be able to connect 100% of the docker-compose up commands (depending on the system) to the postgres service and this will turn out as a failed migration step.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[TheJoin95]

@LobeTia lint is failing but I believe it's going to get fixed with the draft PR #63 , am I right?

[LobeTia]

@LobeTia lint is failing but I believe it's going to get fixed with the draft PR #63 , am I right?

Correct, will be fixed with #63