fix: improved general report reliability

[alecdwm]

New report logic:

• Any analytics event kicks off a general report
• General report is completed async, so that it doesn't block the kickoff event
• General report sets up balances and nft subscriptions, then waits a maximum of 30s for those subscriptions to fully hydrate
  • If they take longer than 30s, we continue to build the report with whatever data has hydrated so far
• Background restarts / browser quits / etc will result in the general report being cancelled,
  but the kickoff event is still sent
• Once general report is completed, it is stored locally.
  At this point it is primed and ready to go, so background restarts / browser quits / etc won't affect the next step
• Completed general report is included in the next analytics event, and when this happens it is cleared from storage

[chidg]

LGTM