[FEATURE] healthy endpoint

When some pod has an issue to connect to the database or any other dependent service, it's still healthy for the loadbalancer which send traffic to it increasing the errors for the customers.

In order to reduce or completely remove the errors during these connection issues I'd like to propose to add a /healtz (yes it's written healthz instead of health to avoid overlapping with any other similar endpoint for the application and it's a common usage to name this one like that for the kubernetes) which will tell the loadbalancer that the pod is not healthy and to stop sending traffic to it. This endpoint will also help kubelet in kubernetes (or any other automated process) to restart that unhealthy pod before it's becoming critical to the whole system.

The issue names no files or tests; start by locating the service's HTTP entry point and checking how database and other dependent-service failures are represented. Determine which dependency failures should make /healthz report the pod as unhealthy for load-balancer and kubelet checks. Done means the endpoint is available and its healthy and failing cases are covered by tests.