Automatic disablement of Customer Cloudant triggers on EAI_AGAIN error ( Network DNS)

[groezing]

If cloudant Provider cannot reach Customer Cloudant DB databases anymore, then the trigger gets automatically disabled ( LOGIC: Assumption is, that customer has deleted its cloudant DB and forgot to disable the iBM Cloud functions trigger) , but this is not always the case.

Regarding the fact that IBM Cfn will sunset the "automatically disablement" of trigger is no more needed.
-> Change logic to do no more any "automatic disablement"

Also there is an unhandled exception in case of a EAI_AGAIN error (DNS error) in the cloudant provide code. Fixing this , too.

Jan 8 17:39:16 cloudanttrigger-01-worker-85fd4b44b8-wqw5t cloudanttrigger-01-worker /cloudantTrigger/node_modules/ibm-cloud-sdk-core/lib/request-wrapper.js:313
var error = new Error();
^
Jan 8 17:39:16 cloudanttrigger-01-worker-85fd4b44b8-wqw5t cloudanttrigger-01-worker Error: getaddrinfo EAI_AGAIN iam.cloud.ibm.com
at RequestWrapper.formatError (/cloudantTrigger/node_modules/ibm-cloud-sdk-core/lib/request-wrapper.js:313:21)
at /cloudantTrigger/node_modules/ibm-cloud-sdk-core/lib/request-wrapper.js:299:45
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
statusText: 'EAI_AGAIN',
body: 'Response not received - no connection was made to the service.'
}