If Caldera executor is enabled and Caldera is down, the platform should fail to start

[SamuelHassine]

Description

If Caldera executor is enabled and Caldera is down, the platform should fail to start

If this is not the case, here is what happens:

1. Platform starting
2. At boot, the platform tries to create the Caldera abilities to launch executor, it fails with:

2024-05-30T19:00:02.743Z ERROR 6 --- [OpenBAS API] [           main] i.o.e.c.service.CalderaExecutorService   : Error creating caldera executor: java.lang.RuntimeException: org.apache.hc.client5.http.ClientProtocolException: Unexpected response for request on: /abilities
2024-05-30T19:00:02.860Z ERROR 6 --- [OpenBAS API] [           main] i.o.e.c.service.CalderaExecutorService   : Error creating caldera executor: java.lang.RuntimeException: org.apache.hc.client5.http.ClientProtocolException: Unexpected response for request on: /abilities
2024-05-30T19:00:02.868Z ERROR 6 --- [OpenBAS API] [lTaskScheduler3] i.o.e.c.client.CalderaExecutorClient     : Cannot retrive agent list

3. When trying to execute something, nothing happens ever, because abilities in Caldera are missing.

[johanah29]

Do we really want our users not to interact with the platform when caldera is down? We have other features that do not depend on caldera to work (sending emails and sms for example).

[jborozco]

As discussed in technical refinement to prevent the whole platform to be down, and let user see his data and prepare other exercises:

In case of executor Caldera being down, show a platform message alerting the user.