Crypto | Be less blind: Analytics, reports, better logs

## Problem

We need more visibility on how many users are seeing crypto problems, and what are the most common cause so that we can efficently affect effort.

## Solution

Get started on the journey to full observability by implementing simple analytics and better logging.

- \[x\] Analytics | Port existing matomo metrics to posthog https://github.com/vector-im/element-meta/issues/34
- \[x\] Analytics | Improve posthog metrics https://github.com/vector-im/element-meta/issues/224
- \[ \] #781
- \[ \] Analytics | Report olm decryption errors \(to\_device messaging\) https://github.com/vector-im/element-meta/issues/234
- \[x\] Logs | Lab option to auto report rageshakes on UTD https://github.com/vector-im/element-meta/issues/37
- \[ \] https://github.com/vector-im/element-meta/issues/114
- \[ \] Logs | UX to send matching rageshake on UTD https://github.com/vector-im/element-meta/issues/123
- \[ \] **Make debugging UISIs easy**
- Discovery:
- Standardize client logs, make it easy to report issues \(from sender or receiver\)
- or R&D realtime observability via Jaeger, see #31
- \[ \] https://github.com/vector-im/element-meta/issues/32
- \[ \] Analytics | Instrument verification
- \[ \] Analytics | Instrument key backup