Better management on API call retry on /graphql errors

[aHenryJard]

Description

When OpenCTI is in bad shape and connectors or worker retry API call there is no sleep time between calls and this can lead to many /graphql calls and ends with:

Max retries exceeded with url: /graphql (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f811e756cf0>: Failed to establish a new connection: [Errno 111] Connection refused'))

Some delay should be add after a failing call to /graphql.

Environment

1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
2. OpenCTI version: { e.g. OpenCTI 1.0.2 }
3. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

1. { e.g. Run ... }
2. { e.g. Click ... }
3. { e.g. Error ... }

Expected Output

{ Please describe what you expected to happen. }

Actual Output

{ Please describe what actually happened. }

Additional information

{ Any additional information, including logs or screenshots if you have any. }