fix(widget): add docker container healthcheck for widget web

[zettlrobert]

What changed? Why was the change needed?

The community edition currently was not starting based on removed healthchecks and container dependencies.

• 🐛 Bug Report: ghcr.io/novuhq/novu/web:2.1.0 docker container STATUS (unhealthy) - curl: not found #7478
• original pr
• @merrcury comment first time contributing to this project let me know if you have additional requirements, if the taken approach is agreeable i will expand on this draft pr
• @Aaron-Ritter feedback is welcome ;)

Screenshots

Details

I added a simple node script to check if the web server is up and running that should set an example on how healthchecks could be integrated after removing the curl dependency has been removed from the base image.

Special notes for your reviewer

Ensure that the environment is configured correctly, all ports and variables are set in the .env file.

For testing purposes, build the novu-web docker image locally, and exchange the cloud image in the community-compose file for the locally available one.

If you want a failing healthcheck you could pass a port that is NOT running in the container to the healthcheck.

# Go to web directory
cd apps/web

# Build docker image
pnpm docker:build

In the docker compose-compose.yaml file replace (just local testing)

    # image: 'ghcr.io/novuhq/novu/web:2.1.1'
    image: novu-web

Spin up the local compose stack

[netlify]

👷 Deploy request for dashboard-v2-novu-staging pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	2f10564

[Aaron-Ritter]

@zettlrobert do we need the same check for all the different containers and not only web? Since I believe the removal of all checks in the pull request #7929 is requiring further consideration. Can we reintroduce this for all the containers?

[zettlrobert]

@zettlrobert do we need the same check for all the different containers and not only web? Since I believe the removal of all checks in the pull request #7929 is requiring further consideration. Can we reintroduce this for all the containers?

@Aaron-Ritter
Yes, it is needed and I can introduce it.
I just wanted some feedback if this approach is okay with the maintainers, as I am quite unfamiliar with the code base and their standards.