Handle errors gracefully for non-critical data requests - #7693

Summary

This PR is a followup of the incident we had during the weekend.
The console does a lot of requests on init, which are not crucial for it to work, so I have logged the errors and just marked the data as unavailable for the time-being, that way the console stays functional. For more important requests, like managed gateway or gateway stats this only happens if the request was aborted with a timeout.

Changes

• Handle gracefully errors on init
• Show info as unavailable for gateways stats and managed gateway requests

Testing

Steps

mock an init request to time out and see that you are still able to log in to the console.
mock the gateway stats request to time out and observe the gateway status panel shows a message.

Results

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• Testing: The steps/process to test this feature are clearly explained including testing for regressions.
• Infrastructure: If infrastructural changes (e.g., new RPC, configuration) are needed, a separate issue is created in the infrastructural repositories.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.