fix: add refreshing errors to the retrieval state, change output level

Description

• add alerts about refreshing errors to the state of the instance (the retrieving section)
• change the output level of data refreshing errors from debug to error

Related issue

Examples

  ...
    "retrieving": {
      "mode": "logical",
      "status": "failed",
      "lastRefresh": "2023-02-04T23:19:54Z",
      "nextRefresh": "2023-02-06T00:00:00Z",
      "alerts": {
        "refresh_failed": {
          "level": "error",
          "count": 1,
          "lastSeen": "2023-02-04T23:19:54Z", 
          "message": "failed to exec restore command: exit_code: 1. Output: pg_restore: warning: could not find where to insert IF EXISTS in statement \"-- *not* dropping schema, since initdb creates it
\"pg_restore: error: could not execute query: ERROR:  column "comment" of relation "key" does not exist
Command was: COPY pgsodium.key (id, status, created, expires, key_type, key_id, key_context, name, associated_data, raw_key, raw_key_nonce, parent_key, comment, user_data) FROM stdin;
pg_restore: error: a worker process died unexpectedly"
        }
      },
      "activity": null
    },
  ...

Checklist

• MR description has been reviewed
• MR changes are functionally tested
• MR does NOT have API/CLI changes OR there are API/CLI changes and they have been reviewed & DOCS ARE ADJUSTED (reference doc, etc)
• MR does NOT have UI changes OR there are UI changes and they have been reviewed & UX IS REVIEWED