feat(deployment): add healthcheck for backend

[AgustinRamiroDiaz]

What

Adds a healthcheck for the backend service

Why

• In other applications I want to build depending on the simulator (feedbuzz, intelligent oracles) I need to depend on this service in order to be able to make calls to it. Healthchecks are the way to go for specifying dependencies between containers
• Healthchecks are a great idea in general

Testing done

• tested the new feature
• tested the bug fix

Decisions made

• I've done it without using the tests module to not introduce module dependencies
• I've done it with a Python script since CURL nor WGET are available in the image

Checks

• I have tested this code
• I have reviewed my own PR
• I have created an issue for this PR
• I have set a descriptive PR title compliant with conventional commits

Reviewing tips

none

User facing release notes

The backend container now has a healthcheck! You can use this to depend on it in your applications building on top of GenLayer's simulator

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 15.35%. Comparing base (8416405) to head (42e1797).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #564   +/-   ##
=======================================
  Coverage   15.35%   15.35%           
=======================================
  Files         112      112           
  Lines        7950     7950           
  Branches      187      187           
=======================================
  Hits         1221     1221           
  Misses       6653     6653           
  Partials       76       76           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarcloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud

[YeagerAI-Bulat]

I wanted to suggest adding a /metrics API endpoint that can expose metrics in Prometheus format. This would be really helpful for monitoring and would allow us to collect and visualize various metrics about the application's behavior.
In addition, we could use this /metrics endpoint to perform health checks. This approach could give us more detailed insights about system health compared to a simple "heartbeat" check, as it would expose more granular metrics, making it easier to track performance and identify issues early on.

[AgustinRamiroDiaz]

@YeagerAI-Bulat I agree, but having a /metrics endpoint is a whole issue in of itself, given that we currently don't have any metrics

Could you create an issue to track this request of having Prometheus metrics?

[github-actions]

🎉 This PR is included in version 0.16.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀