Make all long-running services react to network changes in status-go

[dlipicar]

We have several long-running processes in status-go:

1. Collectibles ownership refresh
2. Balance history checker
3. Transfers detection

Only (1) reacts to network changes in status-go. All others are reset by the client, which is quite error-prone.
Ideally this logic should live in the backend, the client should listen to changes in the results (balances, collectibles, etc) and not handle the business logic.