[Jupiter] Support Failover

[ytvnr]

🌈 Feature

When failover is enabled and the endpoint does not work, then I should fall back to the second one.

🌄 Additional information

When running standalone container tests in Jupiter mode (see this issue), then it appears that the current implementation of FailoverInvoker was not compatible with Jupiter.

Failover document: https://docs.gravitee.io/apim/3.x/apim_publisherguide_backend_services.html#configure_failover

Acceptance Criteria

• Failover feature should work like V3 Gateway

[Sicofonia]

Refined, ready for sprint

[jhaeyaert]

To test it you can enable the Failover on a Jupiter api and configure your backend to point on http://localhost:12332

Run the following command to start listening on the local port: nc -l 12332 -k

Try you api, you should see multiple request coming to your local netcat (1 + N where N is the number of failover attempts).

[LiliaEn]

Tested on the default env v3.19.0
Used the same API to cover both Jupiter and V3 with a webhook site as BE.
The number of requests received on the webhook site is equal to number of failover attempts set +1.