Capture non-DHT related get errors in analytics

Nobody has claimed this yet.

## The Issue
We used to have get failures for reasons outside of sd/blob timeout, but they are no longer being captured. Some examples included: not enough disk space, no access to download location, max kee fee errors, and more exotic ones like `'NoneType' object is not subscriptable`. This can give us additional insights as to why users experience download issues.

## System Configuration

- LBRY Daemon version:
- LBRY App version:
- LBRY Installation ID:
- Operating system:

## Anything Else

## Screenshots

## Internal Use

### Acceptance Criteria
1.
2.
3.

### Definition of Done
- [ ] Tested against acceptance criteria
- [ ] Tested against the assumptions of user story
- [ ] The project builds without errors
- [ ] Unit tests are written and passing
- [ ] Tests on devices/browsers listed in the issue have passed
- [ ] QA performed & issues resolved
- [ ] Refactoring completed
- [ ] Any configuration or build changes documented
- [ ] Documentation updated
- [ ] Peer Code Review performed

No files, tests, or entry points are named. Start by tracing the get failure handling and analytics reporting, then identify where non-DHT errors such as disk-space or download-location failures stop being captured. Done means these errors are recorded in analytics, with unit tests covering the relevant failure cases.

Written by the indexing model from the issue text.