Address issues brought up by Eclipse DB migrations

In the migration, the ECA API went down as the MariaDB instance became completely unresponsive. While betterstack reported the downtime, OKD never "saw" the downtime as the liveness probe wasn't set into the production instance. We should update this in the case of recoverable issues in the service.

A second problem is that the MariaDB being down completely took the service down and stopped it from being able to respond. Do we want the service to be able to run w/o historic data/persistence? While validating incoming requests would be a good idea, none of the historic requests would work. If we want to do this, we'd have to remove the DB from the health check, which according to documentation for Quarkus Datasources is pretty simple, as well as handle that explicitly to stop the calls from melting down.