Check recovery/retry strategy in case of resolver issues

[stitch]

[2024-06-11 08:20:31,034: INFO/ForkPoolWorker-1] Task websecmap.scanners.scanner.internet_nl.status[4793948e-6139-4d27-808c-e26028c85f2f] succeeded in 0.03817895008251071s: (599, {'network_error': 'None ConnectionError(MaxRetryError(\'HTTPSConnectionPool(host=\\'batch.internet.nl\\', port=443): Max retries exceeded with url: /api/batch/v2/requests/0c135d270f5144df82ab90ba04bb3a27 (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7fc9b0a80880>: Failed to resolve \\'batch.internet.nl\\' (Name or service not known: batch.internet.nl using 1 resolver(s))"))\'))'})

Add a standard retry strategy for resolver issues, and use the normal recovery in case this doesn't work out