feat(notify): use logrus to capture errors

[orandin]

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Improvement: use logrus to capture errors from Send Notify to standardize the errors logs.

• What is the current behavior? (You can also link to an open issue here)

The error logs aren't standardized.

• What is the new behavior (if this is a feature change)?

All notify backend use the same function to capture an error and the error logs are standardized.
Also, some fields have been added to simplify the debug.

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

The format of error logs has changed to be standardized with the rest of the application. In case where an alerting system that parses the logs is used, the users need to change their configuration/rules.

• Other information:

An example of notify_config to test the new behaviour:

"notify_config":{
   "test":{
      "type":"webhook",
      "config":{
         "webhook_url":"http://localhost:7777"
      }
   }
}

# Before
2022/10/05 21:31:43 Post "http://localhost:7777": dial tcp [::1]:7777: connect: connection refused

# After
ERRO[2022-10-05T21:26:22+02:00] Error while sending notification on webhook   error="Post \"http://localhost:7777\": dial tcp [::1]:7777: connect: connection refused" instance_id=8 notification_type=task_state_update notifier_name=test notify_backend=webhook task_id=8f971130-cadf-498d-ac3c-50c799e97d50

[ovh-cds]

CDS Report test#1443.0 ✘

• tests and lint
  • golangci-lint ✘
  • unit-test and integration-tests ✔

[rbeuque74]

Build is failing on golangci-lint, feel free to run it on your side to find out the issue ;)

[orandin]

Now, it should be good! 😉

[rbeuque74]

Will re-run the CI on monday!