Issue with detection that node goes offline after switching to `helpy.AsyncHived` implementation / permanent `loading` in the header if there is no connection

FYI: @kmochocki

Previously in the Clive we had a mechanism that would set the offline status on the node if any of the requests failed because of "no response available" (which means we can't connect to the node)

In the batch requests:

In the regular requests:

But since the Node.CachedData is a Clive feature, helpy.AsyncHived does not have such a thing. Looks like there should be a possibility to hook on helpy batch request and regular request and add our own logic if the request has failed.

Because this is broken now, no one can depend on node.cached.online to detect if we have a connection. This can lead to weird bugs because this mechanism is broken.

For example, it can be noticed there:

while previously (before !553 (merged), so on 419e58c0) we had: